Conditional Automations

Conditional automations let you combine any trigger with one or more conditions on the record’s fields. The trigger fires, Blue checks the conditions, and the actions only run if every condition is satisfied. Available on Business and Enterprise plans.

This turns broad triggers like “when a record is updated” into precise rules like “when a record is updated and Status is set to Approved and Total is greater than $10,000”.

Adding conditions

1. Open the workspace’s Automations panel.
2. Edit or create an automation.
3. After picking a trigger, click Add Condition.
4. Pick the field to test, the operator, and the value to compare against.
5. Add more conditions if needed — multiple conditions are combined with AND (all must match).
6. Save.

What you can test

Conditions work against most fields on the record:

• Status — list, completion state
• Custom fields — text, number, currency, percent, date, single/multi-select, checkbox, assignee, reference, lookup, and more
• System fields — created at, updated at, completed at, updated by, assignees, tags, due date
• Computed fields — formula and rollup values

Operators match what’s available in the same field’s filters — equals, is set, is empty, greater than, contains, is one of, date ranges, and so on.

Example

Trigger: Record is moved to a new list Conditions:

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

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

The automation only runs when both conditions hold. Move an unapproved record, or one under $10k, and nothing happens.

Behavior

• Conditions are evaluated at the moment the trigger fires, against the record’s state immediately after the triggering change.
• A condition referencing a field that doesn’t exist on the record evaluates as false — the action does not run.
• The Automations panel shows a run history with the outcome of each condition check, useful for debugging an automation that “doesn’t seem to fire”.