Skip to content

Documentation

Automations

Build rules on a drag-and-drop canvas from six triggers and twelve actions, with an Else path for requests that do not match the conditions. Route, tag, notify, and call webhooks.

Where
Admin → Settings → Automations
Permission
MANAGE_AUTOMATIONS
Updated
October 2026

Overview

A rule has one trigger, a set of conditions, and the steps it runs. There are six triggers and twelve actions to choose from.

A request that matches every condition runs the rule's If path. One that does not runs the Else path, or is skipped when the Else path is empty.

So one rule can route urgent requests one way and everything else another.

Active rules run top to bottom, in the order listed under Admin → Settings → Automations, each time their trigger fires. Drag a rule by its handle to change the order.

When two rules change the same field, the lower rule's change wins.

A rule's actions run in order and stop at the first one that fails. Steps before it stay applied, and nothing after it runs.

A run stopped by a failed action is recorded as Failed in the rule's run history.

A rule never re-runs on a change its own actions caused, directly or through other rules.

A chain of rules triggering each other stops after five. A rule skipped at that limit is recorded as Failed in its run history.

Step by step

  1. 01

    Start from a template or a blank canvas

    Go to Admin → Settings → Automations. The flow on the canvas reads top to bottom: a trigger, a condition, then the steps the rule runs.

    • Templates cover common cases and open pre-filled on the canvas
    • Templates include payroll routing, phishing escalation, urgent alerts, and offboarding webhooks
    • New automation opens a blank canvas
  2. 02

    Choose the trigger

    Click the Trigger node to choose what starts the rule. There are six triggers.

    • Request created
    • Request updated
    • Comment added
    • Status changed
    • Approval decided
    • Request reaches an age (time-based, see the next step)
  3. 03

    Set up a time-based rule

    Request reaches an age fires once a request reaches the age you set.

    • Age is measured from when the request was created, last updated, or moved to its current status
    • It looks at open requests, and at resolved ones when a status condition names Resolved
    • The check runs every 15 minutes
    • Each request fires the rule once until its status changes
    • The age is part of the trigger, so the Else path runs for requests that reached the age but miss the other conditions
  4. 04

    Add conditions

    Drag a condition from the Steps panel onto the Condition node, or click it. Then set its value in the inspector on the right.

    • A request must match every condition on the rule
    • Keywords: look in the subject, description, or requester email; match any or all; add exclude terms; optionally match case
    • With keyword matching, paste a sample subject to see whether it would match
    • Other conditions: request type, status, priority, assigned team or user, approval required, requester department, tags, custom field values
    • Request type, status, priority, and assigned team take an operator: is, is any of, or is none of
    • No match: drop steps onto the Else row to handle it there, or leave the Else path empty to skip it
  5. 05

    Add the steps

    Drag an action from the Steps panel onto the flow, or use the + on a connector. There are twelve actions.

    • Assign: Assign agent, Assign team, Assign least-busy agent
    • Change the request: Set status, Set priority, Add tag, Remove tag
    • Approvals and notes: Create approval, Add internal note
    • Tell people: Send notification, Send email
    • Your systems: Call a webhook, a signed POST to one of your endpoints
  6. 06

    Arrange the steps

    Put the steps in the order they should run and on the right path. Incomplete steps are outlined until they are set.

    • Reorder: drag a step's handle, or use Move up and Move down in the inspector
    • Change path: drag a step to the other path, or use Move to Else and Move to If
    • Webhook calls are sent after the rule's changes are saved
    • Each webhook call is logged in the endpoint's delivery history
  7. 07

    Test, then turn it on

    Save the rule paused and test it against a recent request before it goes live.

    • The test shows which path the rule would take and what it would do
    • Each run is logged as Success or Failed in the rule's run history
    • Each logged run links to the request it changed
    1. Save the rule paused
    2. Run the built-in test against a recent request
    3. Set the switch to Active
    4. Save

Good to know

  • Use Send notification or Send email on the Request created trigger to acknowledge new requests right away.
  • Use Assign least-busy agent to spread new work across a team by current workload, instead of naming one assignee.
  • Put catch-all rules at the top of the list and specific rules below them, so the specific rule's change is the one that sticks.
  • Or give the specific rule an Else path, instead of writing a second rule with the opposite conditions.
  • Use Call a webhook for custom workflows. A signed POST triggers your own script, which can disable an account or update the configuration management database (CMDB) on your own infrastructure.