Introduction
Use Run automation on another device to start a selected automation on a runner device. The device moving through the current automation remains the workflow device, while the selected runner becomes the device for the child automation.
The current automation waits for the child run to finish before it continues.
Prerequisites
Before adding this action:
Create the automation you want to run on the selected device.
Confirm the runner device is available and can perform every action in the target automation.
Create any automation variables you want to map in both the current and target automations.
ℹ️ NOTE: You cannot select the current automation as its own target or select an archived automation.
Add the Action
Open the automation and select Edit.
Select + where you want to add the action.
In the Flow category, select Run automation on another device.
In Runner device, select the device that will run the target automation. The automation runs on the selected device.
In Automation, select the automation to run.
Configure Variable mappings, conditions, and additional options as needed.
Select Save.
Workflow Device and Runner Device Context
This action separates the device moving through the current workflow from the device that runs the target automation.
Context | Device or run used |
Current pipeline and action conditions | Workflow device |
Source values selected in variable mappings | Current automation run for the workflow device |
Target automation actions and device context | Runner device |
Target automation variables | Child run on the runner device |
For example, an automation running for a workstation can start a maintenance automation on a server. The workstation's pipeline waits while the server runs the selected automation.
Each workflow device that reaches this action creates a separate child run. This remains true when several workflow devices use the same runner.
Map Automation Variables
Use Variable mappings to pass values from the current automation into variables defined by the target automation.
Select a variable from the current automation as the source.
Select the corresponding variable in the target automation.
Add another mapping for each value you want to pass.
When the action starts, Level copies the current source value into the mapped target variable for that child run. A target variable without a mapped source value uses its own default value.
💡 TIP: Give related source and target variables clear names so mappings are easy to review later.
Completion, Failure, and Nesting
The current automation waits at this action until the child run finishes.
If the child run succeeds, the action succeeds and the current pipeline continues.
If the child run fails, the action fails.
If the child run is canceled, the action is marked as canceled.
Canceling the parent action also cancels its linked child run.
Use On action failure and retries in Additional options to control how the current pipeline handles a failed action. See Actions Overview for details.
Run automation actions can be nested up to four levels. A call beyond that limit fails with Nesting depth exceeded.
Runner Availability
The runner must be available for the target automation's device actions to run. Its operating system, installed tools, permissions, and network access must meet the requirements of every action in the target automation.
Level tracks active automations that reference a runner device. Remove or replace those references before deleting the runner.
⚠️ WARNING: Before changing a runner, review the target automation and every workflow that uses it. A different runner may not have the same tools, permissions, or network access.
FAQ
Does the target automation run on the workflow device too? No. The child automation runs on the selected runner device. The workflow device's current pipeline waits for it.
Do all target variables need a mapping? No. Unmapped target variables use their defaults.
What happens when several workflow devices reach this action? Each workflow-device step starts and waits for its own child run, even when the steps share the same runner.
Can I select the current automation? No. An automation cannot call itself directly.
Can I select an archived automation? No. Select an active automation.
How deeply can automations call other automations? Run automation actions support up to four nested levels. A deeper call fails.
For the same-device version, see Run Automation Action. For variable details, see Automation Variables.