Automation Conditions

Automation conditions allow you to split the flow of the automation based on the result of a condition check.

Table of Content

• Contact has a specific tag
• Custom Field is set to a specific value
• Advanced Filter
• Note on condition logic

Here are the actions that are available:

Contact has a specific tag

This condition will check to see if a contact has a specific tag. The result will split the flow into two paths - true and false. 

Custom field is set to a specific value

This condition will check to see if the custom field that you selected has a specific value. You can check for any number of values, and a new path will be set for each value. 

Another default path will be added for any contacts that have the custom field not match any of the values.

Advanced filter

This condition will allow you to build a complex check based on several attributes available for you to choose from. The result will split the flow into two paths - true and false. 

For example, if you want to check if a contact has purchased their first package, you can set the condition "Number of packages" "is equal to" 1. If the contact has purchased one package, they will go to the "true" path, otherwise, they will go to the "false" path.

You can combine multiple conditions using AND/OR operators.

In this example below, the automation is checking whether the contact has one package OR one membership, AND if their next event is happening sometime within the next week.

If the contact has a package or a membership, it will check the second part of the condition, and if their booking is within the week, they will go along the true path. If either part of the advanced filter does not apply to the contact, they will go through the False path.

A little about Condition Logic:

• OR filters have a Hierarchy: If there are two conditions, like in the example, if the first statement is true, the system won't check for the second statement. However, if the first statement is not true, it will check the second statement. In the example, if the contact does not have 1 package (could have 0, or more than 1) then the automation will check if they have a membership.
• AND filters require all conditions to be met: In practical terms, if any single condition in an AND set fails (is false), the whole set fails immediately, but for a contact to pass through the True path, every condition must be true. So if in the example the first condition group was changed to an AND option, we would want the system to check if the contact has 1 package AND 1 membership, too. If they do not have one out of the two, then they will go through the False path.
• AND/OR Settings apply between Condition Groups, but can be different inside a condition group. Meaning, if there are more than 2 Condition groups, the system can only have AND or OR settings, not both for the global setting (white background). But within one condition group (pink background), that can be changed from the main setting. In the example, the first condition group is checking package and membership numbers with an OR setting (pink background), but we also want to check if they have an upcoming event date, so between the two condition groups there is an AND setting (white background). If a third condition group was added, like "Total number of visits is more than or equals to 10", then that has to have the AND option selected, too.

To learn more about automations, be sure to check out our overview help article or view the other articles on this feature.

P.S. Join our Facebook group and connect with other OfferingTree users to share questions, offer ideas and insights, and support each other towards a more thriving wellness business.

Register to our monthly Skill Sparks to stay ahead of the curve! This is where we dive into all the new features and updates like Automations feature we just covered. It's the best way to ensure your wellness business is always taking full advantage of the latest tools.