Run subworkflow
Run another workflow of the tenant in-process and continue with its outputs.
Run another workflow of the tenant in-process and continue with its outputs.
When to use it
Call another workflow in the same organisation and continue with its outputs. The referenced process must be available and compatible with the supplied records. Check nested behaviour and output types rather than assuming the child’s results are automatically the parent’s final output.
Add and configure
- Add Run subworkflow from the workflow step picker.
- Give the step a recognisable name and connect its required inputs.
- Set the options below. Nested names identify fields within an object or a list item.
- Validate the recipe, inspect the test result, then run it on the intended data.
The step identifier used in the editor’s code view is subworkflow_run.
Settings
| Setting | Accepted value | Required | Default | What it controls |
|---|---|---|---|---|
Pass Inputs (pass_inputs) | boolean | No | true | When true, the subworkflow's trigger input is the parent step's input_records. When false, the subworkflow runs against an empty input (its DAG roots fire from scratch). |
Workflow Id (workflow_id) | string; format uuid or null | No | null | Target workflow id. Either workflow_id or workflow_name must be set. |
Workflow Name (workflow_name) | string or null | No | null | Target workflow by name (resolved within the same tenant). Convenience for human-authored workflows; agents should prefer workflow_id. |
Inputs and outputs
| Direction | Port | Content | Required | Multiple records |
|---|---|---|---|---|
| Inputs | in | records | Yes | Yes |
| Outputs | out | records | Yes | Yes |
Effects, testing, and recovery
Writes information inside Strive.
The declared preview behaviour is to skip this step. Configuration can affect preview behaviour; HTTP GET is a notable exception. Read dry runs before using a preview with live connections.
No duplicate-prevention key is declared for this step. Do not assume that manually repeating the step is free of repeated effects.
Example: Run a child workflow by id over this step's records
Step settings:
{
"workflow_id": "66666666-6666-4666-8666-666666666666"
}
Example: Run a named workflow from scratch (no inputs handed over)
Step settings:
{
"pass_inputs": false,
"workflow_name": "enrich-contacts"
}
Check the result
Inspect the selected run’s status, counts, errors, and output records. An empty collection can be a valid result, and a completed step can contain per-record failures where the step defines that behaviour. Check the next step’s expected record shape before publishing or delivering the result.