Conditions give you more control of your Automations. They allow you to filter which tasks will start your Automation.
For example, you could set a Trigger for tasks with a particular status and then add a Condition for the Automation to apply to tasks with specific assignees.
Feature availability and limits vary by plan and user role. Learn more
Understand Conditions
In the Automation schema, Conditions are criteria that must be true to run an Automation.
Conditions have to be set before the Trigger for an Action to happen.
Available Conditions
The following conditions can be applied to Automations.
Condition | Description |
Assignee | Filter for specific users, all, or none. |
Current Date Is |
Filter Actions that are triggered before or after a fixed or dynamic date. This Condition doesn't affect the date that the Automation run on. The date range you set for this Condition must be met in order for the Automation to run. |
Custom Field |
Filter for a completely unique task field like a value or a budget.
When using the Custom Field is not equal to Condition with a Label Custom Field, selecting more than one label requires that the value is not equal to both labels, not one or the other. You will need to add an additional Condition for each separate label option. You can use AI Fields and private Custom Fields as Conditions. |
Custom Field using numerical Formula Fields |
Currently, numerical Formula Fields do not work as Conditions. |
Priority | Sift out tasks that don't have a certain priority |
Start Date | Check for tasks with specified start dates. Select a specific date or a before/after date |
Status |
Choose tasks in a certain stage of your workflow. |
Tag | Set your Condition to match any or all selected tags. You can also filter for all tasks that do not contain tags |
Task type | Set your Condition to match a specific task type or all selected task types. |
Time Estimate | Filter out tasks that do/don’t contain estimates. You can also specify a greater than/less than/equal to value for the Condition. |
Time in Status |
Only take action when tasks have been a particular status for a specific amount of time. For example: When a task’s priority changes to urgent, if the task has been in the QA Review status for more than 5 hours, add a comment tagging in the QA team to prioritize testing. |
Watcher |
Filter for specific users, all, or none.
|