As workflows grow, they become hard to read. Sub-workflows let you split big jobs into smaller, reusable parts.
What is a sub-workflow?
It is a normal workflow that another workflow calls using the Execute Workflow node. The parent passes data in and receives results back.
Why use them
- Reuse: one “send notification” workflow used in many places.
- Clarity: each workflow does one clear job.
- Easier fixes: change logic once, not in ten copies.
- Memory: heavy tasks can run separately.
How to design one
Give it a clear input, such as a name and message, and a clear output. Document what it expects in the workflow name or notes.
Cautions
- Do not hide important logic in many tiny pieces; keep a sensible number.
- Errors in a sub-workflow must still be noticed. See error handling.
- Be careful with changes that break callers.
Related
Large lists and batches: looping over items.
Quick answers
What is a sub-workflow?
A workflow called by another using the Execute Workflow node.
Why use sub-workflows?
For reuse, clarity and easier maintenance.
Can sub-workflow errors be missed?
Yes, unless you set up error handling and alerts.
Related reading
- How to Build Your First n8n Workflow: Form to Sheet to Email
- n8n Webhook Node: Test URL vs Production URL Explained
- How to Use the HTTP Request Node in n8n to Call Any API
Not sure where to start?
Tell us your goal, whether it is your own business, freelancing, studies or a job, and we will say honestly if our 15-day live n8n course is the right fit.
See the 15-day n8n training | Find your city | Book free counselling