Sequential Merge Refactor with Count and Key Equivalence Receipt

How it works

1. 1.Manual Trigger starts the run with one empty item
2. 2.Sample Batch Code node emits six demo records shaped {id,type,amount}
3. 3.Sequential Branch Processor validates id, type and numeric amount and routes items to invoices/credits/other/rejected sequentially
4. 4.Each produced item carries expected_total, produced_total and input_index
5. 5.If node compares produced_total to expected_total with strict number validation
6. 6.True path goes through Set adding equivalence_path with includeOtherFields:true
7. 7.False path goes through NoOp into Merge input 2 (append mode, no waiting)
8. 8.Build Equivalence Receipt returns one item with input/output counts, branch counts, sorted key list and the EQUIVALENT verdict

Use cases

• Replace a two-branch + waiting Merge layout that can deadlock when a branch empties
• Separate valid from rejected records while proving no item was lost
• Audit invoice vs credit classification before handing data to another system
• Produce an internal review receipt with per-branch counts and amount totals

Requirements

• n8n 2.45.7 or newer
• No credentials and no external calls needed
• For real data, replace the Sample Batch node with your own source using the same {id,type,amount} schema

Setup and testing in n8n

1. Import the JSON into n8n and run Execute Workflow
2. Confirm the final output is one item with equivalence = EQUIVALENT and output_item_count = 6
3. Empty-branch test: delete all credit records from Sample Batch and rerun; execution completes and branch_counts has no credits key
4. Invalid-input test: strip all ids; every item lands in the rejected branch and total_amount is 0
5. Empty test: make Sample Batch return an empty array; a diagnostic item with branch 'empty' is emitted without hanging

Service Value

Ready-made workflow template for automation delivery and service execution.