The If/Else action allows you to separate contacts who trigger a workflow based on conditions you want them to meet. This helps you fine-tune your workflow and automate common actions that your customers perform. In other words, if there’s any point where you want to split a workflow into different paths, this action will allow you to do so. Let’s check how it works!

Note: When adding a Conditional branch to your workflow, you can select between prebuilt templates or create your own from scratch.

Using Scenario Recipes #

Scenario Recipes are prebuilt If/Else action templates that simplify the setup process. Some will have a few requisites you’ll need to add into the workflow for the recipe to function; these are displayed under its name.

Selecting a scenario will result in prepopulated branches for you to customize to your business needs. Once the premade branches are filled out, you can add any additional conditions, segments, or branches needed.

Build Your Own #

This blank format allows you to build a conditional action that suits your needs. To use it, start by naming the action for easy identification.

Setting Up a Branch #

These will be the conditions the contact needs to meet to qualify for the branch. The available conditions are organized into folders for you to select the specific value or action the contact needs to meet before moving to the next step. Locate fields by skimming through each folder or by using the search function.

You can add multiple conditions for the same branch. Keep in mind that you will have to select between the And/Or operators to define the conditional behavior.

• AND option: When selecting this option, the contact has to meet all conditions added to qualify.
• OR option: When selecting this option, the contact will qualify for this branch if one of the conditions is met.

If you’re looking to mix and match “and/or” logic, you can do so within a branch to build more nuanced conditions.

The None Branch #

A branch is automatically added to perform a series of tasks if the added conditions fail. This branch is called the “None Branch.” It can be renamed, but no conditions can be added to it, and it will always be the last branch.

Once you’ve created your branches, click Save Action to maintain the changes.

Adding Follow-up Actions #

After setting up your branches, you can add actions for each branch, including adding other If/Else actions.

And there you have it! Those are the basics of the If/Else action. As a quick recap, the If/Else action allows you to separate contacts into different action paths depending on the conditions they meet. You can build them from scratch or use a Scenario Recipe as a base, allowing you to automate commonly recurring processes and vary your automation’s behavior.

Frequently Asked Questions #

What does the If/Else action do? #

It splits contacts in a workflow into different paths based on conditions they meet, letting you branch your automation logic.

Do I have to build conditions from scratch? #

No. You can use prebuilt Scenario Recipes that prepopulate branches, or build your own conditional action from a blank template.

Can a single branch use multiple conditions? #

Yes. You can add multiple conditions and choose the AND operator (all must be met) or the OR operator (any one must be met) to define the behavior.

What is the None Branch? #

It is a branch automatically added to handle contacts who fail all the defined conditions. It can be renamed but cannot have conditions added, and it is always the last branch.

Can I add actions after the branches? #

Yes. After setting up your branches you can add follow-up actions to each branch, including additional If/Else actions.

How do I save my If/Else configuration? #

Once your branches are set up, click Save Action to keep the changes.