Step · Subflows
Return from a subflow
Sends a status and output values back to the workflow that called this subflow.
Subflow setup and worked example
Inputs
| Label | Key | Type | Required | Notes |
|---|---|---|---|---|
| Subflow ID | subflow_id | Text | Yes | Map Subflow ID from this run's Start a subflow trigger. |
| Status | status | Choice: Succeeded or Failed | No | Defaults to Succeeded. |
| Output 1 | output_1 | Text | No | |
| Output 2 | output_2 | Text | No | |
| Output 3 | output_3 | Text | No | |
| Output 4 | output_4 | Text | No | |
| Output 5 | output_5 | Text | No |
Outputs
No output fields.
How it behaves
- The result goes back to the waiting Call a subflow step, not to a separate recipient.
- The first return decides the result; later returns do not replace it.
- When the caller chose not to wait, no result is sent back to it.
Errors
Fails when
- Use the Subflow ID from this run's trigger rather than an ID copied from an earlier run.
- If returning fails, check the connection and the runs of both workflows before retrying.
For errors that every step can return, see Troubleshooting.
Example
Send a selected owner back to the calling workflow.
| Input | Value |
|---|---|
| Subflow ID | Map from Start a subflow |
| Status | Succeeded |
| Output 1 | owner@example.com |
The owner email appears on the caller's Call a subflow step, not as a local output from this return step.