Sub-workflow
A modular workflow unit in the n8n automation platform that can be invoked independently by other workflows through the Execute Workflow node. It has its own triggers, node canvas and execution history, supports independent testing, debugging and reuse, and is used to implement modular workflow design.
Timeline (last 90 days)
n8n supports marking a workflow as a "Sub-workflow" so that it can be retrieved via a drop-down list in the editor, and it can be triggered via Webhook or queue mode.
The execution of a sub-workflow consumes a separate execution quota, and the data structures of inputs and outputs must be clearly agreed upon at design time, otherwise parameter passing across processes is prone to errors.
In n8n, compared with true microservices, sub-workflows still run in the same n8n instance, sharing the execution engine and resource quotas, with no independent deployment and no network isolation.
A practical migration strategy is to first get the business logic working in a monolithic workflow, identify the reusable fragments, and then gradually extract them into sub-workflows.
Each sub-workflow can be tested independently, updated independently, and reused by multiple main workflows.
The caller specifies the target sub-workflow through the Execute Workflow node, and can pass structured input parameters and receive its returned results.
All Facts (6)
n8n supports marking a workflow as a "Sub-workflow" so that it can be retrieved via a drop-down list in the editor, and it can be triggered via Webhook or queue mode.
50%UnverifiedThe execution of a sub-workflow consumes a separate execution quota, and the data structures of inputs and outputs must be clearly agreed upon at design time, otherwise parameter passing across processes is prone to errors.
50%UnverifiedIn n8n, compared with true microservices, sub-workflows still run in the same n8n instance, sharing the execution engine and resource quotas, with no independent deployment and no network isolation.
50%UnverifiedA practical migration strategy is to first get the business logic working in a monolithic workflow, identify the reusable fragments, and then gradually extract them into sub-workflows.
50%UnverifiedEach sub-workflow can be tested independently, updated independently, and reused by multiple main workflows.
50%UnverifiedThe caller specifies the target sub-workflow through the Execute Workflow node, and can pass structured input parameters and receive its returned results.
50%