After setting a When step for any supported trigger (task, deal, budget, invoice, project, and more) 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.

⚡️ 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.

⚡️ ⚡️ 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, or commenting on tasks, deals, budgets, invoices, and other supported objects.
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.

📌 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 are the attributes you can use when filtering (adding your conditions), depending on the trigger.

Task, deal, budget, and invoice triggers (click to expand)

TASK	DEAL	BUDGET	INVOICE
Assignee	Budget / deal value	Budget total	Aging (overdue, unsent, paid)
Creator	Company	Budget type (internal or client)	Amount (no tax)
Custom fields	Custom fields	Company	Amount (with tax)
Description	End date	Custom fields	Amount credited (no tax)
Due date	Estimated time	End date	Amount credited (with tax)
Folder	Expected close date	Estimated time	Amount paid
Initial estimate	Last activity	Hours used	Amount unpaid
Last activity	Lost reason	Invoiced percentage	Amount written off
Percentage of remaining time	Owner	Last activity	Company
Project	Pipeline	Owner	Copied to accounting
Remaining time	Pipeline stage	Percentage used	Creation date
Repeated	Probability	Project	Creator
Start date	Sales status	Purchase order number	Credited
Task hierarchy	Start date	Recurring	Currency
Task list	Subsidiary	Revenue	Custom fields
Title	Triggered by	Start date	Due date
Triggered by		Status	Last activity
Type (Milestone or Task)		Subsidiary	Payment date
Worked time		Total time	Payment status
Workflow status		Triggered by	Project(s)
Workflow status category			Sent date
			Sent status
			State
			Status
			Subsidiary
			Tax amount
			Triggered by
			Type

Project, booking, expense, and company triggers (click to expand)

PROJECT	BOOKING	EXPENSE	COMPANY
Amount for invoicing	Absence type	Amount	Billing name
Company	Approval status	Amount (with tax)	City
Creation date	Booking status	Approval status	Company code
Custom fields	Booking type	Billable amount	Country
Estimated time	Company	Company	Creation date
Name	Custom fields	Creation date	Currency
Open revenue	Deal / Budget	Creator	Custom fields
Profit	End date	Currency	Default subsidiary
Project manager	Event	Custom fields	Default tax rate
Project number	Event status	Date	Due days
Project type	Note	Deal / Budget	Email
Status	Person	Description	Last activity
Triggered by	Project	Due date	Name
Worked time	Stage type	Export status	Phone
	Start date	Invoiced	State
	Triggered by	Payment status	Status
		Person	Street
		Profit	Tax ID
		Project	Triggered by
		Recognized revenue	Website
		Reimbursed on	Zip code
		Reimbursement status
		Service
		Service type
		Stage type
		Tax rate
		Triggered by
		Vendor

Employee and form response triggers (click to expand)

EMPLOYEE	FORM RESPONSE
All email addresses	Survey fields (all fields on the submitted form)
Approval policy
City
Company
Country
Creation date
Custom fields
Deactivation date
Email
First name
Job title
Joined date
Last activity
Last name
Manager
Permission set
Phone
State
Status
Street
Subsidiary
Triggered by
Type
Website
Zip code

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.

COMPARATORS

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

Fine-Tuning Automations with "Check if" Steps