Create an Automation Workflow

Triggers define the "when" for an automation and are grouped by event type (for example: movement, speed, safety event, document submitted, or a schedule). When you begin an automation, you choose the relevant trigger first; specificity is not required here because in-trigger conditions, modifiers, and filters narrow the scope later.

Most triggers share the same building blocks: an initial trigger condition, an optional minimum duration so the condition must persist for a set time before the automation fires, filters to limit assets, drivers, or tags, and an optional time filter that defines when the trigger is active (by default triggers are always active).

Triggers cannot be deleted from a workflow; to change a trigger use the Back-to-trigger-selection control. You can also stack secondary (multi) triggers to require multiple simultaneous conditions, but secondary triggers are only available for triggers that support them and are evaluated together with filters and branch conditions so the automation fires only when all are true. The primary (first) trigger determines which actions are available for the workflow; trigger to action and trigger plus modifier to action mappings are documented in the Directory.

Conditions appear in two places: as in-trigger configuration (for example, which fault codes to watch, minimum duration, or tag/asset filters) and as workflow branching rules (conditional branching).

Conditional branching lets a single trigger split into multiple check if / otherwise if paths so the automation runs the first matching branch; branching is evaluated top-to-bottom (order matters), nesting is supported where available, and branches may be left empty purely for routing. In-trigger configurations and modifiers apply first and effectively act as an AND with any branch conditions. Conditional branching is limited to a subset of triggers.

In addition, automations support waits (time-based waits that pause for a configurable interval and event-based waits that pause until a specific event or condition occurs) which are commonly used in conjunction with conditions to delay or await state changes before continuing the workflow.

Actions define the then of an automation and are chosen after the trigger is configured; the action menu only shows actions valid for the selected trigger (and availability can change when a modifier is applied).

Multiple actions can be stacked under the same workflow and each action can be edited or removed. Workflows may also include waits or conditional branches between actions to control timing and routing. Before saving, validate every action card (errors highlight in red) and then save; automation runs and action execution are visible in the Automations dashboard and run/history views for troubleshooting.