Creating and monitoring automations

Open /settings/automations and choose New rule. Select a trigger, define its conditions, and add actions such as notification, assignment, task creation, status advancement, or email. Date-relative and overdue triggers run through bounded scheduled work; event, payment, approval, and other state changes can fire inline.

New rules are saved disabled. Use the dry-run preview to confirm which records would match, then enable the rule deliberately. The run history records matches, action outcomes, retries, and dead-letter failures so an operator can tell whether the rule ran and what happened.

Avoid sending broad email until the recipient and trigger scope are proven in dry run. Disabling a rule stops future evaluations but does not undo completed actions.

Access and roles

Viewing the automation manager and creating, editing, enabling, retrying, or deleting rules requires automations.manage, included in Owner, Admin, and Planner. Custom roles need that capability explicitly. Automation actions still obey their own authorization and data boundaries when dispatched.

Use /help/operational-troubleshooting when a run is failed or produces no match.