Automation
Runs another automation from inside this one, through that automation's On Demand trigger. Reach for it to factor shared work into one automation that several others call, rather than copying the same run of steps into each.
Fields
The action carries one operation, Trigger, with these fields:
| Field | Description |
|---|---|
| Target Automation | The automation to run. |
| Target Trigger | Which of the target's on-demand triggers to start. |
| Input Payload | The structured input to start the run with. Shown when the chosen trigger defines a Content Type payload. |
| Input Payload (JSON) | The input written as a JSON object instead. Shown when the chosen trigger defines a Custom Shape payload. Accepts variables, and must evaluate to an object matching that shape. |
| Wait For Completion | When on, this step waits for the target to finish. When off—the default—it starts the target and continues immediately. |
What later steps see
- Fire and forget, with the wait off: a receipt identifying the run that was started.
- Wait for completion, with the wait on: a completion snapshot carrying the target's outcome, timing, and any error summary. A failed outcome fails this step, so it can follow the node's error path.
Gotchas
The target automation and the trigger inside it are stored as a pair. Deleting the target clears both, and the step then fails at run time saying what is missing rather than blocking the save—which is what lets an imported automation whose target does not exist here still be saved and repaired.