← All N8N workflows
Automation & utilitiesCodeHTTP RequestIfManual TriggerNo Op

Start Multiple Sub-Workflows Asynchronously

Configured with HTTP Request, Respond To Webhook, Loop Over Items, Wait, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerRoutingLoop Over ItemsLoop Over ItemsWaitWebhook Callback WaitWaitCodeUpdate finishedSetCodeTransformInitialize finishedSetEdit FieldsCodeSimulate Multi-Item forParallel ProcessingCodeRoutingIf All FinishedIfWeb / APIStart Sub-Workflow viaWebhookHTTP RequestWeb / APIAcknowledge FinishedRespond To WebhookRoutingContinue Workflow(noop)No OpWaitWaitWaitWeb / APICall Resume on ParentWorkflowHTTP RequestWeb / APIRespond to WebhookRespond To WebhookTriggerWebhookWebhook

Node categories in this workflow

  • Trigger
  • Routing
  • Wait
  • Code
  • Transform
  • Web / API

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
Webhook Callback WaitWaitWaitSee node parameters
Update finishedSetCodeCodeSee node parameters
Initialize finishedSetTransformEdit FieldsSee node parameters
Simulate Multi-Item for Parallel ProcessingCodeCodeSee node parameters
If All FinishedRoutingIfSee node parameters
Start Sub-Workflow via WebhookWeb / APIHTTP RequestPOST
Acknowledge FinishedWeb / APIRespond To WebhookSee node parameters
Continue Workflow (noop)RoutingNo OpSee node parameters
WaitWaitWaitSee node parameters
Call Resume on Parent WorkflowWeb / APIHTTP RequestPOST
Respond to WebhookWeb / APIRespond To WebhookSee node parameters
WebhookTriggerWebhookSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

Start Multiple Sub-Workflows Asynchronously

Start Multiple Sub-Workflows Asynchronously

  • Note: Callback/Webhook "internal" Base-URL should be configured in the n8n instance to reference the k8s service name and internal port.
Main/Parent Workflow

Main/Parent Workflow

  • This starts multiple executions of the sub-workflow in parallel and then loops until they all report back.
Sub-Workflow

Sub-Workflow

Cut/Paste this into a separate workflow, and activate it!!!

Call Resume on Parent Workflow

The callback resumes the parent workflow and reports which item finished. There could be a race condition if the parent workflow was just resumed by a different sub-workflow but hasn't entered a webhook-wait again yet. The delay and retry mitigates for the possibility that multiple subtasks complete and call back at once.

Start Multiple Sub-Workflows Asynchronously

Start Multiple Sub-Workflows Asynchronously

Purpose and structure

This folder contains the Start Multiple Sub-Workflows Asynchronously workflow. Its executable nodes use code, httpRequest, if, manualTrigger, noOp, respondToWebhook, set, splitInBatches, wait, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0629_Wait_Code_Update_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Pseudo-Synchronously Wait for All Sub-Workflows to finish

More in Automation & utilities