How to Run Multiple Workflows in Sequence in n8n

Each child workflow should be designed as a standalone unit that performs one specific task. The first node of each child workflow should be an Execute Workflow Trigger node (not a regular trigger like Schedule or Webhook). This special trigger node receives data from the parent workflow's Execute Workflow node. The child workflow processes the data and outputs results that flow back to the parent. Design each child workflow so it can be tested independently by clicking Execute Workflow with test data.

Create a new workflow that orchestrates the sequence. Add a trigger node (Schedule Trigger, Webhook, or Manual) to start the pipeline. Then add an Execute Workflow node for each child workflow you want to run in sequence. Connect them in order: Trigger > Execute Workflow (Step 1) > Execute Workflow (Step 2) > Execute Workflow (Step 3). In each Execute Workflow node, select the corresponding child workflow from the Workflow dropdown. The output of each Execute Workflow node becomes the input for the next one.

The Execute Workflow node passes all items from its input to the child workflow's Execute Workflow Trigger node. The child workflow receives this data as its input items. In the child workflow, access the data using standard n8n expressions like {{ $json.fieldName }}. When the child workflow finishes, its last node's output is returned to the parent workflow as the Execute Workflow node's output. This creates a seamless data pipeline between workflows.

1// In the child workflow's first Code node:
2// Access data passed from the parent
3const inputData = $input.all();
4
5const results = inputData.map(item => {
6  return {
7    json: {
8      // Process the data
9      processedField: item.json.rawField.toUpperCase(),
10      timestamp: new Date().toISOString(),
11      source: 'Step 1 - Transform'
12    }
13  };
14});
15
16return results;

Sometimes you need a delay between workflow steps — for example, waiting for an external system to process data before querying it. Insert a Wait node between Execute Workflow nodes in the parent workflow. Configure the Wait node with the Resume option set to After Time Interval, and specify the delay in minutes or seconds. The workflow pauses at the Wait node and resumes after the specified interval, then continues to the next Execute Workflow node.

If a child workflow fails, the Execute Workflow node in the parent workflow will also fail, stopping the entire pipeline. To handle this gracefully, set the On Error option on each Execute Workflow node to Continue (using error output). This creates a second output that captures error details instead of stopping the pipeline. Connect the error output to notification nodes or fallback logic. You can also create an Error Trigger workflow that monitors the parent workflow for failures.