Introduction
Actions are the individual steps an automation executes when it runs. Each action performs one operation on a device — running a script, restarting the system, applying a tag, setting a custom field, and so on. You chain them together in a pipeline that runs top to bottom.
Automation Pipeline
The automation canvas shows the trigger and actions as connected steps. Actions run in order, one at a time per device.
Select an action on the canvas to open its side panel. To change its settings, select Edit action in the panel.
On the canvas, each action step shows:
The action name and icon
Condition and variable indicators when configured
A handle for reordering the step
A step menu with Edit, Enable or Disable, Clone, and Delete, when you have permission to edit
💡 TIP: Drag an action step's handle on the canvas to change its position. Triggers don’t have an order; any trigger can start a run for a matching device.
Adding an Action
To add an action to a pipeline that already has actions, select the inline + at the position where you want to insert it, then choose Add another action. On an empty canvas, select Add an action.
The action picker opens. Browse by category or use the Search actions field.
Select the action. Its edit form opens in the side panel.
Configure the step, then click Save.
Available Actions
System — Run scripts on the workflow device or a selected runner, restart devices, manage processes and services, and interact with the Windows registry.
ℹ️ NOTE: Run script and Shell execute on the device moving through the automation. The "on another device" actions execute on a selected runner, while system variables, automation variables, and custom fields keep the workflow device's context.
Flow — Control automation execution with approvals, runtime input, logged-in user waits, delays, branching, and nested automation calls.
Files — Download files to a device from a direct URL or other source.
Level — Manage device state within Level: custom fields, alerts, tags, groups, maintenance mode, and device deletion.
Resolve alert closes an active alert for the current device that was raised by the selected Create alert action in the same automation.
Security — Install OS updates, manage Windows Defender, and control disk encryption.
App Management — Install, uninstall, and upgrade applications using Winget, Homebrew, and Linux package managers.
Notifications — Notify technicians or end users via in-app alerts, SMS, or email.
Other — Make outbound HTTP requests to external systems.
ℹ️ NOTE: The action list above links to dedicated articles when one is available. The options in this article (Additional options, Conditions) apply to every action regardless of category.
Reordering Actions
Drag an action step's handle on the canvas to move it to a new position in the pipeline.
Enabling and Disabling Actions
Each action has an enabled switch in its side panel header. You can also open the step menu on the canvas and choose Disable or Enable. Disabling an action skips it entirely during a run, which is useful when you want to temporarily remove a step without deleting it.
Additional Options
Every action has an Additional options section at the bottom of its configuration panel. Expand it to access these settings.
Action name
An optional custom label for this action. When set, it replaces the default name (e.g., “Shell: PowerShell”) on the pipeline card. Useful for making long pipelines readable at a glance.
On action failure
Controls what happens when this action fails.
Option | Behavior |
Fail pipeline | The run stops for this device. Subsequent actions don’t run. |
Suppress and continue | The failure is noted but the run continues to the next action. |
Default is Fail pipeline.
💡 TIP: Use Suppress and continue when you’re handling failure yourself later in the pipeline. For example: set Install Windows Updates to Suppress and continue, capture its output to a variable, then add a Create Alert action (with an Action status = Failed condition) that only fires if the update action failed. Without Suppress and continue, a failed update would halt the pipeline before the alert ever runs.
Assign action output to variable
Captures the output of this action and stores it in an automation variable. Select an existing variable from the dropdown, or click + Create new variable to define one.
Once captured, the variable is available for use in subsequent actions and in Variable conditions on any action that follows.
Retries
How many times Level retries this action if it fails. Default is 0 (no retries). Enter a whole number.
ℹ️ NOTE: Retries apply before the On action failure behavior kicks in. If you set 3 retries and the action fails all 3 times, then the On action failure setting determines what happens next.
Enabled
Toggles this action on or off. Identical to the toggle on the pipeline card.
Conditions
Every action also has a Conditions section that lets you restrict when it runs. Conditions are evaluated per device at runtime — if a device doesn’t meet them, the action is skipped for that device while the pipeline continues.
See Action Conditions for the full reference on all condition types, operators, and values.
FAQ
Can I have two actions of the same type in one pipeline? Yes. Add the same action type multiple times — each instance is configured independently. This is useful when you need to run the same operation with different parameters, or use Action status conditions to branch between outcomes.
What’s the difference between disabling an action and deleting it? Disabling keeps the action in the pipeline but skips it during runs. Deleting removes it entirely. Use disable when you want to temporarily pause a step without losing its configuration.
If an action fails and I have “Fail pipeline” set, does it affect other devices in the same run? No. Each device runs the pipeline independently. A failure on one device doesn’t affect other devices in the same run.
Can I capture output from any action type, or just scripts? The Assign action output to variable option appears on all actions, but what gets captured depends on the action. Script-based actions (Shell, Run script) capture the script’s stdout. For other action types, check the individual action article for what output is available.
Who can add or modify actions? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.