Use Automation Conditions

Conditions give you more control of your Automations. For example, you could set a Trigger for tasks with a particular status and then add a Condition to complete the Automation only for particular Assignees.

Learn which Conditions are available to fine-tune your Automations!

What you'll need

  • The Workspace admin or owner must enable the Automation ClickApp.
  • Guests can't set up Automations.
  • The number of total active Automations that you can have in your Workspace depends on your plan:
    • Free Forever: 5 total active Automations.
    • Unlimited: 500 total active Automations.
    • Business and above: Unlimited total active Automations.
  • The number of Actions that can be completed per month depends on your plan:
    • Free Forever: 100 Actions/month.
    • Unlimited: 1,000 Actions/month.
    • Business: 10,000 Actions/Month. 
    • Business Plus: 25,000 Actions/month. 
    • Enterprise: 250,000 Actions/month. 
  • Action limits reset on the first of every month (PST).
  • Usage alert emails are sent to owners and admins of Workspaces when an Automations usage is at 90% and when usage is over 100%.
  • Business Plans and above can purchase more Automation Actions.
  • Webhook actions and Automation integrations are available for Business Plans and above.

Understand Conditions

In the Automation schema, the Condition is criteria that must be true to run an Automation.

Conditions have to be set before the Trigger for an Action to happen.

2024-02-28_10-28-04.png

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.

  • is equal to: Only tasks with identical Custom Field values.
  • is not equal to: Tasks that have a different Custom Field value. 
  • is set: Tasks where the Custom Field is set. 
  • is not set: Tasks where the Custom Field is not set. 

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 private Custom Fields as Conditions.

Custom Field using numerical Formula Fields

Filter for numeric Formula Custom Fields, using the following Conditions:

  • is equal to: Only tasks with identical Custom Field values.
  • is not equal to: Tasks that have a different Custom Field value. 
  • is set: Tasks where the Custom Field is set. 
  • is not set: Tasks where the Custom Field is not set. 
Due Date

Select a specific date or a before/after date.

For an Automation triggered by the task status changing from Any Status to Closed, the Current date is 5 days after the closed date Condition will stop the Automation from firing.

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.
Watcher
Filter for specific users, all, or none.

 

Was this article helpful?