Automation actions are the steps in a pipeline where work gets done! Some actions are pre-built, and others (like scripts) allow for total customization and flexibility. Some actions do work on devices, and others help you do work inside the Level app itself.

Once an action type is selected, any parameters specific to that action (if any) will be revealed. Every action has a required "condition" parameter, as well as additional optional parameters.

System Actions

Restart

This action will restart the targeted devices.

Run Script

This action will run a script from your Level script library.

Please note that unless the script exits in a failure state, the default behavior is for the pipeline to continue to run (even if the script itself fails). Therefore, controlling the exit type will play an important role in flow control of the automation. In PowerShell, Bash, and others use "exit 1" to exit the script in an error state.

See the On Action Failure section below for more details on how an action handles a failure.



Shell

This action is similar to a script, however the script commands can be entered into the action itself. The script commands will not be saved to the script library, and will only exist in the automation. This is useful if the commands required are simple and code reuse is not a concern.

Flow Actions

Wait For Approval

This action will stop all devices in the automation pipeline until a Level technician approves the device to move along in the pipeline.

When a device is pending approval, it will show in the active device status pane on the left, and an icon representing the device will appear next to the Wait For Approval step in the pipeline.

Delay

This action will insert a timed delay step in the pipeline. The duration is in seconds.

Notification Actions

User Approval

This action will prompt the end user of the device to approve or reject this step of the pipeline. The question field is where the desired text to be sent to the end user should go. The Prompt Frequency controls when a reprompt should appear in the event that the delay button is pressed.

The Force Compliance checkbox means that the delay button will no longer be an option after the max attempt value has been reached. After that, the only option the device end user will have is an accept button.

The notification only pushes to a user session logged in to the console. This means it will not work for other sessions including those using Microsoft Remote Desktop Protocol.

Notify User

This action will send a toast notification to the device end user. The notification has no impact on the pipeline flow and only serves to send a notice to the end user of the device.

The notification only pushes to a user session logged in to the console. This means it will not work for other sessions including those using Microsoft Remote Desktop Protocol.

Security

Windows Defender Update

This action will trigger Windows Defender to update its security signatures/definitions. The "Add Level to Windows Defender as an exclusion" option adds Level to Defender's file exclusion list.

Windows Defender Scan

This action will start a full system scan with Windows Defender. The "Add Level to Windows Defender as an exclusion" option adds Level to Defender's file exclusion list.

Level Actions

Level actions do not actually do anything or run any code on the devices. Instead they run actions in the Level app that pertain to organization and management of devices.

Apply Tags

This action step will apply a Level tag to a device.

Remove Tags

This action step will remove a Level tag from a device.

Assign to Group

This action step will move an agent into the group selected.

Enable Maintenance Mode

This action step will put the device into maintenance mode in Level. When a device is in maintenance mode, the device will not trigger alerts from monitor policies. This is a useful action if the other steps in the pipeline are likely to cause the agent to trigger monitor policies.

Disable Maintenance Mode

This action step will disable maintenance mode on a device.

Conditions

Conditions control the scope of devices upon which an action will be run. While conditions are mandatory on triggers to define the initial set of devices, adding conditions to actions is optional. This is useful for targeting specific subsets of devices that meet additional criteria inside the trigger's scope.

Conditions are conjunctive, meaning that when multiple conditions are applied to an action, all conditions must be met for the action to execute on a device. For instance:

  • If one condition specifies "Platform equals Windows" and another specifies "Tag equals Server," only devices that are both Windows platforms and tagged as Servers will match.

This ensures precise control over where and how actions are applied, enhancing targeted device management.

An example action condition choosing only Windows 10 and 11 devices.

Additional Options

  1. Action Name - This field will replace the default name of the action

  2. On Action Failure - This parameter will determine if the pipeline should continue in the event that the script does not exit cleanly.

    • The default option "Fail pipeline" means that if the script does not exit cleanly on a particular device, that the device will exit the automation and the remaining actions in the pipeline will be skipped.
    • The other option "Suppress and Continue" means that in the event of an unclean exit on a device, the next step in the pipeline for that device will be run.
  3. Retries - This integer defines the number of times the Action will be rerun in the event of an Action exiting with a failure state.

  4. Enabled - When an action is disabled, it will not be used as a step in the pipeline.