Skip to main content
All CollectionsAutomationsSetting Up Automations
Fine-Tuning Automations with "Check if" Steps
Fine-Tuning Automations with "Check if" Steps

Set up a "Check if" step as an additional step in the automation building process to refine your automation rule.

Updated over a week ago

After setting a "When" step for tasks, budgets, deals, or invoices, you can enhance your Automation rule by adding a "Check if" step.

Adding a "Check if" step is optional, but it allows you to add another layer of precision to your automation, ensuring it executes only under specific circumstances.

⚡️ Example using only When and Then steps: When a new task is created in a designated project, then send a message to a designated Slack channel.

⚡️ ⚡️ Example of using one When step, two Check if steps, and one Then step: When a new task is created with Alex Taylor as the assignee and the task status is not Closed, then send a message to a designated Slack channel.

Before we delve into the process of adding "Check if" steps, let's brush up on our automation vocabulary 📚:

  • When (Trigger): "When" steps initiate automations by specifying actions such as creating, updating, closing, or commenting on tasks, deals, budgets, and invoices.

  • Check if (Condition): "Check if" steps refine automations by specifying additional criteria that must be met for the automation to proceed. They provide a way to add precision to your automation rules.

  • Then (Action): Actions produce the desired outcomes once all conditions are met. They represent the "then" part of the when-then equation.

Besides those, we also have:

  • Attributes: Attributes are distinct properties linked to triggers (When steps) that provide critical data for the automation. They include details such as task assignee, deal owner, or budget revenue.

  • Comparators: Comparators are tools used to compare conditions within automations. They determine whether a specific attribute meets certain criteria, such as being equal to, greater than, less than, or not equal to a specified value.

Adding a "Check if" Step to an Automation

1) Select and apply the "When" step.

2) Choose the "Check if" option to add a condition.

3) Define the condition attribute, such as task assignee or invoice due date.

4) Select the attribute comparator to specify the condition criteria.

5) Add additional condition rules if necessary.

5)Expand the condition by adding a new condition set, if needed.

6) Save the Check if step and proceed to the next step: defining the "Then" step.

🤖 A "Check if" step is made up of condition sets, and each set can contain individual condition rules.

🤖 Even when grouped into sets, a single "Check if" step can have up to 10 individual condition rules!

Condition Attributes

Here is a list of all attributes for each When step (Task, Deal, Budget, Invoice).





  • Assignee

  • Creator

  • Custom fields

  • Due date

  • Initial estimate

  • Remaining time

  • Start date

  • Task list

  • Title

  • Type (Milestone or Task)

  • Workflow status

  • Worked time

  • Company

  • Custom fields

  • End date

  • Expected close date

  • Lost reason

  • Owner

  • Pipeline stage

  • Probability

  • Sales status

  • Start date

  • Budget type (internal or client)

  • Company

  • Custom fields

  • End date

  • Hours used

  • Invoiced percentage

  • Owner

  • Percentage used

  • Project type

  • Revenue

  • Start date

  • Aging (overdue, unsent, paid)

  • Amount (no tax)

  • Amount (with tax)

  • Amount credited (no tax)

  • Amount credited (with tax)

  • Amount paid

  • Amount unpaid

  • Amount written off

  • Company

  • Copied to accounting

  • Creation date

  • Creator

  • Credited

  • Currency

  • Due date

  • Payment date

  • Payment status

  • Sent date

  • Sent status

  • State

  • Status

  • Subsidiary

  • Tax amount

  • Type

Condition Comparators

Here is a list of all available comparators.

Keep in mind that the availability of comparators depends on the selected attribute and the "When" step.

For example, the attribute "Deal owner" will only support comparators like is, is not, was, and was not, while the attribute "Deal start date" will include more comparator options such as is, was, is not, was not, is or isn't empty, is more than or equal to, is less than or equal to, etc.


  • Is

  • Was

  • Is not

  • Was not

  • Is more than

  • Was more than

  • Is less than

  • Was less than

  • Is more than or equal to

  • Was more than or equal to

  • Is less than or equal to

  • Was less than or equal to

  • Contains

  • Contained

  • Does not contain

  • Did not contain

  • Has changed

  • Has not changed

  • Has changed to

  • Has changed from

  • Is empty

  • Is not empty

  • Has passed

Did this answer your question?