Triggering Conditional Actions
The If/Else workflow function activates upon meeting a predefined condition, directing contacts to subsequent workflow steps. This tool is ideal for segmenting workflows based on criteria like tags or custom values.
Crafting Conditional Logic
To integrate If/Else logic into your workflow, begin by defining a condition that aligns with your goal. Once named, you can continue to the implementation steps.
Branching Strategies
Incorporating branches into a workflow allows for the creation of complex conditional paths, with each branch capable of handling up to 10 unique outcomes. This feature lets you add tailored automation sequences at the end of each branch.
Naming Branches: Assign a clear, purpose-driven name to each branch for easy identification.
Setting Branch Details: Choose the appropriate conditional trigger.
Selecting Operators: From the dropdown, pick an operator that matches your condition. Add the necessary parameters and values.
Adding Conditions: Insert one or more conditions within a branch to refine the logic.
Creating Segments: Click the + Add Segment icon to introduce additional segments, each with its own conditions and filters.
Expanding with Additional Branches: Include more branches as required for your tasks.
Segmenting Workflows
Segments are crucial when diversifying workflow paths. This section allows you to select conditions and operators tailored to your workflow.
Enhancing Logic with 'And' & 'Or'
'And' Logic: Use this when multiple conditions must be met simultaneously.
'Or' Logic: Apply this when you want the workflow to proceed if any one of the set conditions is satisfied.
Duplicating and Reordering Branches
Duplicating Branches: Easily copy a branch within a conditional action by selecting “Duplicate Branch” from the branch menu. The duplicate will appear with "(copy)" appended to the name, ready for renaming.
Reordering Branches: Rearrange multiple branches within a conditional action to better suit changing requirements. This is done by dragging and dropping after selecting the “Reorder Branches” button.
Renaming the None Branch: The “None Branch” is the default branch that handles unmet conditions. This branch can be renamed to better reflect the actions it performs.
Applying Conditional Logic: A Practical Example
Consider a scenario where a client named John provides home repair services. After an appointment, the system sends John a message with three scenarios to choose from. Based on his selection, the system executes a specific workflow:
Showed and Purchased: Triggers actions like adding a "Won" tag and sending a thank you message.
No-Show: Initiates actions such as tagging the contact as "No Show" and enrolling them in a follow-up email sequence.
Each branch results in a distinct set of workflow actions tailored to the selected scenario.
When all configurations are complete, save and publish the workflow to put your logic into action.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article