Workflow Editor
The workflow editor opens as its own full page whenever you create or edit a rule. You assemble the rule graphically: cards for triggers, conditions, and actions are placed on the canvas and connected — from "When this happens" to "Then do this".
Features Overview
Choosing a Starting Point
When creating a new rule, you choose how to begin:
| Start | Description |
|---|---|
| Blank | You build the rule from scratch yourself |
| Description | You describe in your own words what should happen — the AI creates a draft rule |
| Template | You start with a ready-made rule template and adapt it |
Trigger
Every rule starts with exactly one trigger — the event it reacts to (e.g. "Checkpoint scanned" or "Incident created"). The trigger determines which condition fields and placeholders are available in the rule.
Conditions
Condition cards narrow down when the rule actually runs. You choose the field from a list matching the trigger — for the "Checkpoint scanned" trigger, for example, checkpoint, employee, or "photo present"; for incidents, for example, category or severity.
Actions
What should happen when trigger and conditions match:
- Notification — to selected recipients via the channels email, SMS, call, push, and in-app, with a selectable template
- Create task — automatically creates a task in the "Tasks & Routes" workspace
- Escalation — first offers the takeover to one group; if nobody responds within the deadline, it automatically moves to the next level
Validation Before Saving
The editor continuously checks the rule for completeness — for example, missing connections, empty recipients, or unreachable cards. Errors and hints appear directly on the affected cards and in the validation panel; the rule cannot be saved while errors remain open.
Test Run
Before saving, you simulate the rule with sample data: the test run shows which cards would be traversed, which recipients are determined, and what the notification would look like — without anything being sent. You can adjust the sample data in the test dialog.
Scope & Name
In the header area, you can optionally limit the rule to a property or customer and assign a name. If you save without a name, the rule automatically receives one ("Automation N").
Good to Know
:::tip Note
- Editing an existing rule opens the same editor with the rule loaded.
- A rule limited to a property only reacts to events of that property.
- The test run has no side effects — no real notifications are sent and no tasks are created. :::
Permissions
:::info Permission To create or edit rules, you need the Create/edit automation permission. Contact your administrator if you do not have access. :::