Automation workflows
A process is a guided routine a person works through step by step. An automation workflow is the opposite: a background rule that reacts to an event and carries out, unattended, what you defined once. The two exist side by side and should not be confused — use the Visual process builder for routines involving people, workflows for anything that should happen by itself.
#Triggers
A workflow listens for exactly one trigger:
| Trigger | Fires when … |
|---|---|
asset.created | an asset is created |
asset.assigned | an asset's assignment changes |
asset.status_change | an asset's status changes |
ticket.created | a ticket is created |
movement.completed | a movement completes fully |
Every trigger carries data about the event. A condition map filters on it — an empty condition matches every event.
#Actions
When an event matches, the workflow runs its actions in order.
| Action | Effect |
|---|---|
send_notification | Sends someone a notification with a title and body |
assign_user | Assigns an asset to a person |
set_asset_status | Sets an asset to a particular status |
More action types follow in later releases.
#The builder
The builder has three columns:
- Trigger on the left — choose the trigger and define conditions
- Actions in the middle — add, reorder and remove actions
- Inspector on the right — edit the selected action's type and parameters
The Active switch pauses a workflow without deleting it — the quickest route when a rule fires unexpectedly.
#Dry run
Before a workflow goes live you check it with a dry run. You supply a sample event; the workflow runs through without changing data. For each action you see success or failure and, where meaningful, a preview of what would be written. Dry runs are logged and can be reviewed later.
#Permissions
Only holders of admin may create, edit, delete and test workflows. Everyone else sees the builder read-only.
#Reliability
Workflows run on a best-effort basis, and that is deliberate:
- If one action fails, the remaining ones still run
- A failure in a workflow never rolls back the operation that triggered it — an asset creation stands even if the notification hanging off it fails
- Errors are logged and can be reviewed afterwards
Every workflow applies to its own tenant only. One tenant's workflows are invisible to others — see Tenant isolation.