Skip to main content
All CollectionsAutomationWorkflows
Part 1: “Workflows: If/Else Conditions”
Part 1: “Workflows: If/Else Conditions”

This video will go over the IF/ELSE Conditions in Workflows. Please note there are 3 parts to this video.

D
Written by Daina
Updated over a week ago

Please note: There is a limit of 10 branches per condition action.

The below article will show you how to use the if/else condition in a workflow as well as how it works. This condition is very helpful as you can set different actions to happen depending on which condition occurs all in the one workflow.

Navigate to the ‘Automation’ tab in your account and either create a new workflow or click into the workflow you would like to add this condition in.

To add the if/else condition, click the ‘+’ icon to add an action in your workflow.

You can then locate the if/else condition and click to select this action.

If/else conditions are made up of branches, segments and conditions. Branches are the different paths that make up your condition. You can have up to 10 different branches per if/else condition and they are made up of segments and conditions which is what determines which branch a particular contact will fall under.

In order for a contact to follow a particular path or branch, it needs to fulfil the conditions within each segment under that particular branch. You can also add multiple conditions in a segment which can be created as AND or OR conditions. AND meaning both conditions under this segment have to be met in order for them to follow down this branch. OR meaning either of the conditions under this segment have to be met in order for them to follow down this branch.

Similarly, you can also have multiple segments under a branch when you can also apply as AND or OR segments where the contact would either have to meet the requirements of all or only one of the segments to follow down this branch.

Once you have added your if/else condition, you can then add your condition/s.

In the below example, let’s say we want contacts who have a specific tag to continue the rest of the steps in the workflow however if they don’t have the tag, we don’t want them to progress through the workflow. We can set our condition to be tag > includes > and select the tag, in this example the tag is ‘cbd’. Once this is done, we can name our condition ‘Does the contact have the tag CBD?’ and we can then name our branch ‘Yes'. Once this is done, save the action.

You can then see you have two branches created: the one we just created and a ‘None’ branch. This means if the condition is not fulfilled, we can set different actions to occur or none at all in this case so the workflow simply ends.

Now, if you want to further customise this and add multiple conditions, segments or branches, you can do this.

For example, you could create an additional segment where you wanted the tag to include Facebook AND the current day of month is after the 2nd.

So you can see we have two segments, the first segment has one condition and the second has two conditions:

This means, if a contact is tagged cbd they will enter this workflow OR if the contact is tagged Facebook AND the current day of the month is after the 2nd, they will also be able to enter this workflow. This is where the and/or selector is very helpful to determine what requirements you would like someone to fulfil before proceeding through the rest of the workflow steps.

Finally, you also have the option to add additional branches. For example, if we wanted a second branch where someone is tagged ‘bounced email’ we can set this up like so:

From here, you can see we now have three branches where you can set up different actions to occur under each branch.

Did this answer your question?