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 pipeline is the visual sequence of actions that runs when a trigger fires. Actions execute in order, from top to bottom, one at a time per device.
Each action card in the pipeline shows:
A drag handle (left edge) for reordering
A status indicator showing whether the action is correctly configured
A category breadcrumb (e.g., System > Restart)
The action name (default or custom)
An enabled/disabled toggle
A 3-dot menu for additional options
💡 TIP: Actions can be reordered at any time in edit mode by dragging. Triggers don't have an order — they fire independently, and any trigger that fires can kick off the automation.
Adding an Action
Actions can only be added in edit mode. Click Edit in the top-right corner if you're not already there.
Click the + button in the pipeline where you want to insert the action — between existing actions, or at the end of the pipeline.
The action picker opens. Browse by category or use the Search actions field.
Click the action to add it. The configuration panel opens immediately.
Configure the step, then click Save.
Available Actions
System — Run scripts, restart devices, manage processes and services, and interact with the Windows registry.
Restart
Run script
Shell
Start process
Stop process
Manage service
Set registry key
Delete registry key
Flow — Control automation execution with approvals, delays, branching, and nested automation calls.
Wait for approval
Run automation
Delay
Exit automation
Files — Download files to a device from a direct URL or other source.
Download file
Download file via URL
Level — Manage device state within Level: custom fields, alerts, tags, groups, maintenance mode, and device deletion.
Set custom field
Create alert
Apply tags
Remove tags
Assign to group
Enable maintenance mode
Disable maintenance mode
Delete device
Security — Install OS updates, manage Windows Defender, and control disk encryption.
Install Windows updates
Install macOS updates
Install Linux updates
Windows Defender update
Windows Defender scan
Enable disk encryption
Disable disk encryption
Rotate disk encryption key
App Management — Install, uninstall, and upgrade applications using Winget or Homebrew.
Upgrade Winget package
Uninstall Winget package
Install Winget package
Install Winget
Install Microsoft 365 for Windows
Install Microsoft 365 for macOS
Install Homebrew
Install Homebrew package
Upgrade Homebrew package
Uninstall Homebrew package
Notifications — Notify technicians or end users via in-app alerts, SMS, or email.
User approval
Notify user
Send SMS
Send email
Send email report
Other — Make outbound HTTP requests to external systems.
HTTP request
ℹ️ NOTE: Each action links to a dedicated article covering its step configuration. The options in this article (Additional options, Conditions) apply to every action regardless of category.
Reordering Actions
In edit mode, drag any action card by its handle (the grid of dots on the left) to move it to a new position in the pipeline.
Enabling and Disabling Actions
Each action has an Enabled toggle on its pipeline card. Disabling an action skips it entirely during a run — useful for temporarily removing a step without deleting it.
The same toggle is also available inside the action's configuration panel under Additional options.
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.