Add to Automation Step
Add to automation starts a new run of the selected automation. The current run then continues through its own Next output. The step is available in For dialogs and Background automations.
Select the automation to start
Add Add to automation from the step catalog and open its settings. In Automation, select the workflow to start.
The target automation must have a published version with a Start step and must accept new runs. An automation cannot start itself.
A For dialogs automation can start either type. When the current run has a lead, dialog, channel, or source message, this context is passed to the new run. A Background automation can start only another Background automation.
The re-entry setting on the target graph's Start step determines whether the same lead or dialog gets a parallel run, replaces the previous run, or skips the new start.
Pass variables to the new run
In the New run variables block, add mappings between the current and target automations:
- In Pass from, select a Run, Lead, Dialog, or Project variable. Lead and Dialog are unavailable in a Background automation.
- In New run, select the variable name in the target automation.
- Repeat for the remaining values. You can add up to 100 mappings.
The source and target names can differ. For example, the current run's order_total can be passed to amount in the new run. A target variable cannot be filled twice in one step.
On the source side, you can enter a path to a field inside an object or array. On the target side, enter a regular new-run variable name without dots; nested paths are not supported in that field.
The target list is built from the selected automation's published graph. If its variables cannot be loaded or the required name is not used yet, create the name directly in the field. It cannot contain a dot, start with $, have surrounding spaces, or use a reserved system prefix.
Verify the data before starting
Every selected source variable must have a value when the step runs. If a variable has not been set, the step fails and the new run is not started. Add Change variable before this action when necessary, or use a condition to verify that the value has already been received.
JSON-compatible values are passed: text, number, Yes / no, null, array, or object. In the new run, they are available as regular run variables such as {{run.amount}}.
After publication, inspect both runs in the Runs dialog. The source run contains the start action, while the created run has its own history and initial variables.