Conditions in Automations
Conditions control which devices are included in an automation. They are mandatory for triggers to define the initial set of devices but optional for actions, where they further refine the scope within the trigger’s selection.
How Conditions Work
Conditions are conjunctive, meaning that all conditions must be met for a device to qualify. For example:
If one condition specifies "Platform equals Windows" and another specifies "Tag equals Server," only devices that are both Windows-based and tagged as a Server will match.
This ensures precise targeting of devices within automations.
Available Conditions
Condition Type | Description | Availability |
All Devices | No conditions, all devices will be subject to Automation. | Triggers |
Platform | Filter by the operating system (Windows, macOS, Linux). | Triggers, Actions |
Tag | Match devices based on assigned tags. | Triggers, Actions |
Group | Limit to devices within a specific group. | Triggers, Actions |
Status | Filter by device status (online, offline). | Triggers, Actions |
Hostname | Target specific devices by their hostname. | Triggers, Actions |
OS | Match devices based on the installed OS version (e.g., Windows 11, macOS 14). | Actions |
Type | Filter by device type (workstation, server). | Actions |
Custom Field | Use custom fields assigned at the device, group, or global level. | Actions |
Variable | Use dynamically assigned custom variables in automations. | Actions |
Action Status | Filter based on the result of previous actions (success, skipped, failed). | Actions |
By applying conditions, you ensure that automations only execute on the intended devices, reducing unnecessary execution and improving workflow efficiency.
Additional Options
Trigger-Specific Options
Most triggers (except Manual Only) include additional parameters:
Condition (Required) – Determines which devices match the trigger when activated. A broad scope (e.g., "All devices") is usually not ideal, so refining conditions is recommended.
Trigger Name (Optional) – Replaces the default name for better identification.
Enabled (Optional) – If disabled, the trigger won't activate, even if conditions are met.
Action-Specific Options
Action Name – Overrides the default action name for easier identification.
On Action Failure – Defines how the automation proceeds if an action fails:
Fail Pipeline (Default): The automation stops for the affected device.
Suppress and Continue: The automation continues to the next step, even if the action fails.
Assign Action Output to Variable – Stores action output in a variable for later use.
Retries – Specifies the number of retries if an action fails before stopping.
Enabled – If disabled, the action won't execute as part of the automation.