Objects
Object workflows
Bind versioned Workflow Studio templates to object lifecycle events.
Object workflows
Object workflows bind Workflow Studio templates to object lifecycle events. Use them when a record create or update should start a repeatable, versioned process such as review, fulfilment, approval, enrichment, or escalation.
How it works
An object workflow connects an object to a workflow template group. The template group owns versions, and one template version can be published as the active version. The backend stores workflow nodes and edges as JSON and also normalises each node into node-template records for execution, parent relationships, decision paths, and tool connections.
Configure an object workflow
- Open the object and go to Automations or Workflows.
- Create a workflow template group or choose an existing one.
- Add a Trigger node that describes the record event that should start the process.
- Build the process using task, decision, approval, action, Iris, tools, script, route, delay, loop, escalation, and end nodes.
- Save the graph, test it in the playground, then publish the intended version.
- Watch automation jobs and logs after the first live runs.
Design guidance
Keep the trigger narrow. A create trigger is best for onboarding or intake, while update triggers should include enough trigger data or decision logic to avoid firing on every minor record edit. Use the canonical node reference rather than duplicating node behaviour in object-specific notes.