
If/Else Condition - Automation Guides
If/Else Condition - Automation Guides

Contents:
Overview
Example
Mechanics
Date type field conditions
Overview
The "If/Else Condition" action in your automation workflow allows you to fork the contact's journey based on specific conditions. This is useful for creating personalized and dynamic workflows that adapt to your contact's behaviours.
Action Name
If/Else Condition
Action Description
The "If/Else Condition" action evaluates a specified condition and directs the contact down different branches based on whether the condition is met or not. This enables you to tailor subsequent actions according to the contact’s engagement or characteristics.
Action Details

Example: Follow-Up Based on Email Engagement
Scenario: Your business sends a promotional email to customers, and you want to follow up differently based on whether they opened the email or not.
Solution using the "If/Else Condition" action:
Trigger: The workflow starts when a promotional email is sent.
Action 1: If/Else Condition to check if the email was opened.
Condition: Email Event is Opened.
Yes Branch: If the email was opened, send a thank-you email with a special offer.
No Branch: If the email was not opened, resend the promotional email with a different subject line.
Steps to Implement:
Add the If/Else Condition action to your workflow after sending the promotional email.
Set the Condition to "Email Event is Opened".
Configure the Yes Branch to follow up with a thank-you email and a special offer.
Configure the No Branch to resend the promotional email with a different subject line.
This approach ensures that you engage customers based on their interaction with your initial email, making your follow-up more relevant and effective.
If/Else Action Mechanics
When using Includes/ Does Not Include as a condition:
Please Note:
There are several conditional parameters in Workflow Builder where you'll have the option to specify "Includes" or "Does not include" such as Tags and other multiple-option custom fields (checkbox fields, dropdown pickers, etc.)Creating an And condition:
In the example below we are using the AND condition. The system is searching to make sure that the contact Tags - "Does NOT include" both the 'consultation_booked' AND 'consultation_confirmed' tags.

If one of the two tags is present on the respective contact, then the condition will fail.
In this example in order for this contact to go down the "YES" path, both tags would NOT be present on the contact profile/record.
Creating an Or Condition
If your intention is to create an "OR" scenario, you would want to break the two tags into separate conditions and choose the OR option like this:

In this case, if the contact meets ONE or both of the "Or tags" then the condition is true. The system is only looking for one or both conditions to be correct before pushing the contact down the "Yes" path.
More info: If/ Else Conditions - Troubleshooting AND or OR conditions
If/ Else Branches
Please Note:
If or else branches support up to 10 different outcomes per event.What happens when two branches are both true? Will the lead go down both paths?
No, the system will push the lead down the first correct path/branch in your setup. So it goes top down in the order you built the conditions/branches.
Time Comparison Operators
Time Comparison Operators are essential components in workflows used to compare the current date and time with a specified input value. These operators enable workflow automation systems to make informed decisions based on time conditions. The different date and time units that can be compared using these operators include the current day of the week, the current day of the month, the current month, the current year, and the current hour.


Once you choose the specific Time Parameter for which you want to use a Time Comparison Operator for, you need to choose the Time Comparison Operator from the drop down for Select Operator:

The "Is" Operator

The "Is" comparison operator checks whether the selected date unit is the same as the input value. For instance, "Current Day of the Week Is Monday" will only return true if today is Monday. Similarly, "Current Month Is January" will only return true if it is currently January. For the options like Current day of the Month is, you need to specify the date of the current month like the 1st, 2nd, 3rd .

The "Is Not" Operator
The "Is not" operator, on the other hand, checks if the selected date unit is different than the provided input. For instance, "Current Day of the Week Is Not Saturday" will return true for all days except Saturday.

The "Is After" Operator
The "Is after" operator checks if the selected date unit is after the provided input. However, in the case of hours, this operator only considers minutes that start on the next hour. For instance, "Current Hour Is After 6 PM" will only return true if the time is 7:00 PM onwards because 6:59 PM is still considered inside of 6 PM.

The "Is on or After" Operator
The "Is on or after" operator checks if the selected date unit is on or after the provided input. For hours, this operator considers minutes from the same hour and onwards. For instance, "Current Hour Is On or After 6 PM" will return true for 6:59 PM because it is considered to be "On" 6 PM. And it will also be true for any time after 6PM because of the on or After logic in it.

The "Is before" Operator
The "Is before" operator checks if the selected date unit is before the provided input. For example, "Current Month Is Before June" will return true for all months before June.

The "Is on or before" Operator
The "Is on or before" operator checks if the selected date unit is on or before the provided input. For hours, this operator also considers minutes from the same hour. For instance, "Current Hour Is On or Before 6 PM" will return true for 6:59 PM because it is considered to be "On" 6 PM.

The "Is not empty" or "Is empty" Operator
Lastly, the "Is not empty" operator checks if the field has a value, while the "Is empty" operator checks if the field does not have any value. These two operators are used to ensure that the workflow automation system receives valid input values.
Date type field conditions
Compare any Date type field with the following conditions in the If/Else Action:

Condition based on recent days
Today, Tomorrow, Yesterday

Condition based on number of days/weeks/months/years
After, Before, In the Next, In the Last

Condition based on a particular date
On, After date, Before date



