Conditional Automations

Run actions when a record starts or stops matching a saved set of conditions.


Conditional automations run when a record starts or stops matching saved conditions. They are a separate automation type and do not use an event trigger.

Conditional automations require Pro or Enterprise.

Create a Conditional Automation

  1. Open the workspace’s Automations list.
  2. Select Create Automation > Conditional Automation.
  3. Select Matches conditions or Stops matching.
  4. In Conditions, select a field, operator, and comparison value.
  5. Add more rules or groups as needed. Use the filter controls to choose AND or OR logic.

Conditional automation setup with the Matches conditions / Stops matching selector and AND-grouped condition rules 6. Add one or more actions in Then. 7. Select Create Automation. Blue starts tracking whether records match the conditions.

Available Conditions

You can create conditions for most record fields:

  • Status: List and completion state.
  • Custom fields: Text, number, currency, percent, date, select, checkbox, assignee, reference, lookup, and other supported types.
  • System fields: Created at, updated at, completed at, updated by, assignees, tags, and due date.
  • Computed fields: Formula and rollup values.

Each field provides applicable filter operators. These can include equals, is set, is empty, greater than, contains, is one of, and date ranges.

Example

Transition: Record starts matching Conditions:

  • Status = “Approved”
  • Total > 10,000

Actions: Send an email to the finance team and assign a reviewer.

The automation runs when a record changes from not matching both conditions to matching both. It does not run again while the record remains in that state.

Behavior

  • Matches conditions runs only when a record enters the matching state.
  • Stops matching runs only when a record leaves the matching state.
  • Blue records the current matching state when you create or edit the automation. Existing matching records do not run merely because you created it.
  • If a required field is absent or empty, the record must satisfy the selected operator before the automation runs.