Merge n8n Runs Into One List After Loops (Code Node)

Merge items from multiple n8n “runs” into one clean list after loops

If your n8n automations use loops, you may end up with the same task’s output scattered across different runs. This workflow uses a Code node to merge those items into a single list, so you can continue processing everything as one cohesive dataset.

What this workflow does

The workflow is designed for the common post-loop problem: loop executions often leave you with items spread across separate runs. Instead of manually stitching outputs together, this workflow consolidates them automatically.

• Runs a loop-based flow (where outputs may be separated into multiple executions/runs).
• Uses a Code node to combine the items from those different runs.
• Outputs a single run with one unified list, making downstream steps easier to manage.
• Includes a note to adjust the node name inside the Code node as needed for your setup.

This idea is based on an older n8n workflow template focused on merging data across multiple executions.

Use cases

• Batch processing workflows: When you split work into batches and need one final list of results.
• Loop-driven enrichment: If each loop iteration produces items in different runs, merge them for a single export or database write.
• SaaS operations reporting: Consolidate loop outputs before calculating metrics or generating a combined response payload.

Technical details

• Manual Trigger
• Split in Batches
• Wait and No Op (for loop orchestration)
• if (conditional logic)
• Code node (merges items into a single list after loops)

Category: n8n automation workflow. Built for n8n users, automation engineers, and SaaS operators who want cleaner data flow after loop executions.