SIGNALS Docs
Reader View

Workflow Record Triggers

Choose record lifecycle events and understand permissions, deleted records and loop protection.

Record lifecycle triggers

Choose When something happens, expand a business area, then choose a record type. Created, Changed, Deleted and Restored appear before other events. Search by record type, event name or description. The picker hides records you cannot view; an existing selection remains labelled when your access changes.

Lifecycle triggers cover catalogue and pricing records, vehicles, facilities, services, warehouses, route stops, virtual stock intakes, equipment tests, asset deletion, communication and document templates, reports and option lists. Restored is available only where the record already supports restoration. Attachments remain coming soon because they inherit access from their parent record. Exports remain coming soon because they are private files for the person who requested them. Excluded types show their reason in the picker. Identity, tax and currency configuration also remain catalogue-only.

Changed events ignore timestamp-only updates, search fields and sensitive fields. When an event has no change snapshot, it can still start a workflow, but the list of changed fields is empty. Deleted events retain the last saved details when the live record is gone; the run log explains when it uses those details. Steps that need a live record still enforce that requirement.

The workflow service principal must have the record's view capability and access to its warehouse. Deleted snapshots without enough warehouse information are refused for warehouse-restricted principals. A refused trigger records a readable reason. Changes made by a workflow carry its chain identity: record lifecycle triggers cannot restart the same workflow for the same subject in that chain, and incoming domain events at depth five stop. Custom events retain their existing depth-five chain behaviour. Existing stored trigger values and event payload versions are unchanged.

Workflow-made changes use the same lifecycle events as staff changes, including changed_fields where the event supplies them. Update record skips matching values, so a workflow that sets fixed values on its own trigger record settles after a no-op. Values that keep changing remain subject to the depth-five limit; core record events also retain their same-workflow guard. History identifies the workflow, run and step responsible.

Rental transitions and asset status

Choose the rental State changed event (rental.state_changed) for document-state transitions. Filter trigger.payload.from and trigger.payload.to to the transition you need: for order confirmation use from = quote and to = order. Make quote moves enquiry to quote; Confirm order moves quote to order.

Use rental.asset_status_changed for asset-assignment status changes. It is separate from the rental's document state. Webhook subscriptions use these same event names and their from / to payload values. The approval gate for confirming an order is rental.transition.order; it is a command target, not a separate state-change webhook event.