The job of this console
Build or edit the graph, keep a draft until the path is right, then return to the studio to publish. Pause a live rule in the studio before you reshape it here.
Admin · Automation
Automation Rules
Build trigger → condition → action graphs, save drafts, then publish from the studio.
Scroll to Flowcharts. Scenario: Build and publish an automation rule.
Graph editor
Trigger, condition, action — drafts stay silent
Automation rules is the graph editor: trigger → condition → action. Save drafts, then publish from the studio. A draft never fires against live events.
Admin → Workflow automation → Rule builder
Route
/admin/automation-rules
Org flag automationRulesEnabled
HR Admin · Org Admin
Seat at the table
The same administrators who own Workflow studio. Contributors do not get a builder. Partners should not receive export of graphs with production URLs without review.
The working rhythm
Open a rule, edit trigger and conditions, attach actions (notify, route, connector), save draft, publish from the studio. Use notification templates for copy.
Moments that bring you here
A new leave type needs a follow-on mail. An SLA breach should open a ticket. After a connector change. When a published graph mis-routes and must be paused first.
ⓘ
Studio publishes; builder structures
This page does not replace Workflow studio as the operations desk. Notification copy still comes from notification templates.
Flowcharts
1 — Build a rule
Pick a trigger, add conditions and actions, save draft, then publish.
flowchart TD
A[Open Rule builder] --> B[Select trigger]
B --> C[Add conditions]
C --> D[Add actions]
D --> E[Save draft]
E --> F[Publish]
F --> G[Studio shows live]
- 1Open Rule builderAdmin → Workflow automation → Rule builder.
- 2TriggerDomain event the rule listens to.
- 3Conditions & actionsKeep graphs small and testable.
- 4Save then publishDrafts do not fire.
Overview
The builder writes workflow configuration records. Actions must call approved canonical services — never a disconnected table.
How to use
1. One trigger per rule
Split complex graphs.
2. Test with a sandbox event
Publish only after a dry run.
3. Studio for ops
Pause/resume without opening the builder.