Source Completion Gate Before Merge with Documented Waiting Queue

How it works

1. 1.Run Manual Trigger; Code emits fictional branch data including invalid rows
2. 2.Each branch normalizes fields, skips rows lacking orderId, and appends an __statusCard with counts
3. 3.Merge append gathers cards and rows into one channel
4. 4.Completion Gate Check emits one item with per-source status and waiting list
5. 5.If routes complete runs to Set stamping then a final single-output Code; incomplete runs go to NoOp

Use cases

• Preventing duplicate or partial Merge output when both branches fire
• Documenting waiting sources before issuing merged reports
• Unifying CRM and ERP data into one auditable output

Requirements

• n8n 2.44.6
• Only manualTrigger/code/set/if/merge/noOp/stickyNote nodes
• No credentials, no external calls

Setup and testing in n8n

1. Import the JSON, run Manual Trigger, verify one final output with crm=2 and erp=2
2. Remove erp rows and set declaredEmpty:true to verify the complete path with zero
3. Empty a branch without declaring and verify NoOp shows the waiting source with count 0

Service Value

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