Automation Workflows
Overview
Automation Workflows let you react automatically to events inside your tenant. A workflow listens to one trigger (for example Asset created or Ticket created), optionally filters events by a set of conditions, and runs one or more actions when the filter matches.
Automation Workflows are a separate system from the Process Editor. Processes are guided, multi-step flows that a human walks through; automation workflows are background rules that fire on events, unattended.
Triggers
The first release supports five triggers:
| Trigger | Fires when… |
|---|---|
asset.created | A new asset is created |
asset.assigned | An asset's Assigned to user changes |
asset.status_change | An asset's status changes |
ticket.created | A new ticket is created |
movement.completed | A movement is fully completed |
Each trigger carries a JSON payload describing the event. You can filter on any field of the payload using a simple key/value map (dot-notation is supported for nested fields).
Actions
A workflow executes actions in order. If one action fails, the remaining actions still run — the failure is recorded but never rolls back the business event that triggered the workflow.
| Action | Parameters |
|---|---|
send_notification | recipient_id (UUID), title, body |
assign_user | entity_type ("asset"), entity_id (UUID), user_id (UUID) |
set_asset_status | asset_id (UUID), status (e.g. in_use, in_stock) |
More action types will be added in future releases.
Builder
The builder has a three-column layout:
- Trigger (left): choose the trigger and write conditions as JSON. An empty
{}matches every event. - Actions (middle): add, reorder and remove actions. Click an action to configure it.
- Inspector (right): edit the selected action's type and parameters.
Save your changes with the Save button. Toggle Enabled to activate or pause a workflow without deleting it.
Dry-run
The Dry run button opens a drawer with a test payload (JSON) and runs the workflow without touching any business data. Every action result is shown with success/failure status and, where relevant, a preview of what would have been written. Dry-runs are logged so you can audit test activity.
Permissions
Only users with the admin permission can create, edit, delete or dry-run a workflow. Non-admins see the builder in read-only mode.
Safety & reliability
Workflows are best-effort: a workflow error never rolls back the parent write (an asset create, a ticket create, or a movement complete). Errors are logged and can be reviewed later.
Every workflow is scoped to its tenant through tenant isolation. Workflows from one tenant are invisible to every other tenant.