The New Automation Builder: Understanding Conditions Operators

5 min read
This article refers to the new automation builder that is currently being released. If you're not seeing this version, then see our article about the previous version of the automation builder.
Conditions let you create complex automation flows by defining criteria for continuing the flow. 
  • In the THEN path, the automation flow continues only if the condition is met. 
  • In the ELSE path, you can define what happens if the condition isn’t met.
For conditions to work effectively, make sure to select the correct operator (e.g. "is greater than", "contains") and follow the best practices described in this article.
In this article, learn more about conditions that use:

Text operators

Text operators are used for comparing names, labels, etc.
A screenshot of the available text operators.
Best practice: Use text operators for properties that are text strings, for example when a restaurant name is exactly "Paulie's Pizza".

Number operators

Number operators are used for comparing any numerical property, like quantities.
A screenshot of the available number operators.
Best practice: Use number operators for properties that will always be numbers, for example sending an email when a reservation party size is greater than 10.

Date and time operators

Date and time operators are used for comparing date and time properties to specific dates and times.
A screenshot of the available date and time operators.
Best practice: Use date and time operators when you're basing a condition on an exact date or time, for example contacting all customers who made a purchase this month.

Array (list) operators

Array operators are used to specify a list of multiple values or objects, instead of selecting just one.
A screenshot of the available array operators.
Best practice: Use array operators when you're including a specific list of products in your automation, for example shirts sold in your store.

True/false operators

True/false operators are used for comparing any boolean properties that will always be true or false.
A screenshot of the available true/false operators.
Best practice: Use true/false operators for properties that will always be one of two states, for example a checkbox that is ticked or unticked.
Looking for more capabilities?

Did this help?

|