Run Workflow
The Run Workflow block allows a parent workflow to launch one or more child workflows as separate execution units.
Spawn and execute child workflows from a parent workflow
The Run Workflow block allows a parent workflow to launch one or more child workflows as separate execution units. Each child workflow runs in its own isolated context, meaning it does not share variables, scope, or state with the parent workflow. Communication between parent and child happens through explicitly mapped input and output variables, which are configured in the block's settings using the input and output variable properties.
The block is configured with an app ID identifying the target workflow to run, along with a default transition ID that determines where the parent workflow continues after the child completes. An optional display name can be set for identification within the workflow editor. Input variables are passed to the child workflow as launch variables, and the child workflow must be set up with an End block that returns output variables back to the parent.
This block fits into workflows that need to delegate work to reusable sub-workflows, run modular logic in isolation, or coordinate multi-step processes across separate workflow definitions. Because child workflows operate in fully separate scopes, this block is suited for cases where clean separation of logic is required and where the child workflow has been explicitly designed to accept inputs and return outputs.
What you can build
Real-world workflows powered by the Run Workflow block.
Modular Content Generation
A parent workflow delegates article drafting to a dedicated child workflow, passing topic and tone as launch variables and receiving the finished draft as a return variable.
Parallel Data Processing
A parent workflow spawns multiple child workflows to process different data segments independently, then collects their outputs for aggregation.
Reusable Validation Logic
A shared validation workflow is called from multiple parent workflows, receiving input data and returning a pass/fail result without duplicating logic.
Multi-Step Customer Onboarding
An onboarding parent workflow triggers separate child workflows for account setup, welcome email, and CRM entry, each operating in its own isolated scope.
Isolated AI Inference Tasks
A parent workflow calls a child workflow configured with specific AI model settings to perform a classification task, keeping model logic separate from the main flow.
Report Assembly Pipeline
A reporting workflow spawns child workflows to fetch and format data from different sources, then combines their returned outputs into a final report.
Ready to add Run Workflow to your workflow?
Get Started FreeCommon questions about Run Workflow
What are the required parameters for the Run Workflow block?
The block requires an app ID identifying the target child workflow to run, and a default transition ID that controls where the parent workflow proceeds after the child finishes. A display name is optional and used for labeling the block within the editor.
What does the Run Workflow block return?
The block returns output variables that are explicitly passed back from the child workflow via its End block. The output variable properties in the block configuration define how those returned values are mapped back into the parent workflow's scope.
Can the child workflow access variables from the parent workflow?
No. Child workflows execute in their own isolated contexts and do not have access to any variables or state from the parent workflow. Data must be explicitly passed in through launch variables configured in the block's input variable mapping.
What kinds of workflows commonly use the Run Workflow block?
This block is used in workflows that need to delegate logic to reusable sub-workflows, coordinate multi-step processes across separate workflow definitions, or run isolated tasks that have been designed to accept inputs and return outputs through an End block.
Does the child workflow need any special configuration to work with this block?
Yes. The child workflow must be configured to receive launch variables as inputs and must include an End block that returns output variables. Without this setup, data cannot be exchanged between the parent and child workflows.
Related capabilities
Start
Specifies how the workflow is invoked
User Input
Prompt the user for one or more pieces of data that will be saved as a variable. Can include text, multiple choice, images, or files.
Run Function
Execute a custom JavaScript or Python function
Chat
Start a chat session with an LLM.
End
End the workflow. Optionally return a structured output (for API) or send notifications.
Jump
Transition to another workflow, maintaining the same scope
Add Run Workflow to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.