Pattern for Parallel Sub-Workflow Execution Followed by Wait-For-All Loop

n8n template #2536

Summary

What this workflow does This (set of) workflow(s) shows how to start multiple sub-workflows, asynchronously, in parallel, and then wait for all of them to complete. Normally sub-workflows would need to be run synchronously, in series, or, if they are executed asynchronously (to run concurrently, in parallel), there is no easy way to merge/wait for an arbitrary number of them to complete. This is a "design pattern" template to show one approach for running multiple, data-driven instances of a sub-workflow "asynchronously," in parallel (instead of running them one at a time in series), but still prevent the later steps in the workflow from continuing until all of the sub-workflows have reporte

How to set it up

Open template #2536 on n8n.io and click Use for free, or copy the template JSON and paste it onto an empty canvas in n8n.
No app accounts to connect: every node is built into n8n.
Click Execute workflow and step through each node's output to confirm the data looks right.
Toggle the workflow to Active so its trigger runs on its own.

Hand off to your agent

Prompt

Help me set up the n8n workflow "Pattern for Parallel Sub-Workflow Execution Followed by Wait-For-All Loop" (https://n8n.io/workflows/2536). It uses: HTTP Request, Code. Import the template JSON into my n8n instance, list every credential I need to create, and walk me through testing it.

Paste into Claude Code and it will do the rest.

Apps and nodes

HTTP Request Code

Questions

Yes. Hubschrauber published it free on n8n.io as a verified creator, and it has 8,144 views. It runs on n8n Cloud or a self-hosted n8n instance.

None. All 2 nodes are built into n8n.

Similar workflows

NameViews