Run Flow
On this page
Purpose
Run Flow runs a saved flow from the current flow. It is a beta component that creates inputs for the selected child flow and adapts the first child result as Message, Data, or DataFrame.
When to use it
- Reuse a stable subflow.
- Run a child flow after a condition is met.
- Expose a focused child flow as an Agent tool.
Required setup
Create and save the target flow first. Give it clearly named inputs and prefer one output. The parent flow does not pass its input to the child automatically.
How to use it
Tool Mode
- Add Run Flow and select a focused child flow. The Tool Mode toggle appears only after a flow is selected, and only when the selected flow has at least one generated input that is not marked advanced.
- Enable Tool Mode.
- Connect the tool output to Agent Core and test the generated inputs.
Normal mode
- Select Flow Name and fill or connect the generated child-flow input fields.
- Connect one Message, Data, or DataFrame output.
- Recheck generated inputs after changing Flow Name.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Flow Name | Selects the saved child flow and creates its input fields. | Start with a small saved flow. |
| Generated inputs | One field for each input of the selected child flow. In Tool Mode, the Agent can fill only those the child flow does not mark as advanced. | Connect each required value explicitly. |
| Session ID | Names a session for the child flow, used only when the parent flow has none. The parent's session wins. | Leave it unset in normal parent flows. |
| Tool Mode | Exposes the child flow as an Agent tool. | Use a child flow with a clear description and narrow inputs. |
Expected result
Changing Flow Name changes the generated inputs and can require reconnecting them. Run Flow adapts the first result from the child run. It does not select a child output by matching type, so use a child flow with one clear output. Reading more than one Run Flow result port can run the child more than once and repeat side effects or provider charges. Run Flow is not supported in deployed agent flows.
Reference details
The child flow runs under the parent's session, so anything it stores for the conversation joins the parent's history rather than a separate one.
Use If-Else before Run Flow when a child flow is conditional. In Tool Mode, the selected child flow's description becomes the Agent tool description.