A condition is a filter added to an automation trigger so the automation runs only when field values match, for example Status is Complete. Add up to 15 conditions per trigger and combine them with AND (all must be true) or OR (any one is enough).
Plan Availability | All plan types |
Permissions | Administrators or Solution Managers: Can set up and manage conditions in automations. |
Platform | Web |
Related Reading |
What can conditions do?
Precision Filtering: Use conditions to define specific scenarios where automations should execute.
Logical Operators: Choose between AND (all conditions must be true) or OR (only one condition must be true).
Multiple Conditions: Add up to 15 conditions per trigger.
How do I add a condition?
Create or Edit an Automation:
Navigate to your desired Solution and access Automations.
Add a Trigger:
Select the trigger that will initiate the automation (e.g., Record Created).
Define Conditions:
Click Add Condition.
Select the field to evaluate and configure the operator and value (e.g., “Status is Complete”).
Combine Logic:
Use the AND/OR buttons to determine whether all or just one condition needs to be true.
Which operators are available for each field type?
Each field type has specific operators available. The full list:
Field Type | Operators |
Numeric Fields | Auto Number, Count, Currency, Formula (Numeric), Number, Percent, Rating, etc. |
| - |
| - |
| - |
Text Fields | Address, Text, Text Area, Title, Email, etc. |
| - |
|
|
| - |
Assignment Fields | Assigned To, Linked Records, Tags, Multiple Select, Single Select, Status |
| - |
| - |
| - |
| - |
Date Fields | Due Date, Date Range (Start/End), First Created On, Last Updated On |
| - |
| - |
| - |
Special Fields | Checklist, SmartDoc |
| - Checklist: |
| - SmartDoc: |
What are typical conditions?
1. Approval workflow
Scenario: Trigger automation only when a task’s status is marked as “Pending Approval.”
Condition Setup:
Field: Status
Operator: Is
Value: Pending Approval
2. Notify on overdue tasks
Scenario: Send a notification if a task's due date has passed.
Condition Setup:
Field: Due Date
Operator: Is Before
Value: Today’s Date
3. Monitor record changes
Scenario: Run automation when a field value changes (e.g., Priority changes from Low to High).
Condition Setup:
Field: Priority
Operator: Changes (From/To)
Value: Low → High
What keeps conditions manageable?
Combine Logic: Use AND for stricter filters and OR for broader criteria.
Test Your Automation: Simulate different scenarios to verify conditions work as expected.
Limit Complexity: While you can add up to 15 conditions, simpler logic is easier to manage and troubleshoot.
Frequently asked questions
How do I run an automation only when a specific field changes?
Use the When a record is updated trigger and add a condition with the Changes (From/To) operator on that field. The Changes operator is offered only for record-update triggers, which is why it does not appear under other triggers.
My Linked Record field only offers Has any of and Is not empty. How do I detect a change to it?
Those are the operators for the When a record matches a condition trigger. Switch the trigger to When a record is updated and the Changes (From/To) operator becomes available for Linked Record fields.
How many conditions can one trigger have?
Up to 15. Keep the logic as short as you can; simpler conditions are easier to test and troubleshoot.
Can I mix AND and OR?
Each condition set is either AND (all conditions must be true) or OR (one condition is enough). For mixed logic, split the work into two automations.
How do I trigger something a set number of days before or after a date?
Use a date condition such as Is Before or Is After with a relative value, for example Due Date is before today, on the When a record matches a condition trigger.
Last verified 21 Oct 2026 against this article as Product wrote it in Feb 2025 (operators table and the 15-condition limit) and the Automation Triggers article