Guide Your Workflow to Different Paths Using the "Branch" Logic

Keragon’s Branch logic allows you to control the flow of your workflows based on specific conditions. With this, you can create dynamic and intelligent automations that adapt to different scenarios by splitting the workflow into multiple paths.

When to Use the Branch Logic

  • Execute different actions based on user attributes (e.g., gender, subscription status).

  • Route leads or tickets to appropriate teams based on priority.

  • Handle different data scenarios without duplicating workflows.

How to Use the Branch Logic

00:00: This guide will walk you through the process of branching within York Aragon workflow. 00:06: Click the plus icon in your canvas to add a new action. 00:10: Navigate and select logic tab. 00:13: Select the branch logic action. 00:16: Choose the branch step in your editor. 00:19: Select the first Branch path. 00:22: Click and rename the branch to something meaningful. 00:26: Add a new condition to the branch. 00:29: Clicking value, 12, map it with any data from your previous steps. 00:34: Choose the select option. 00:37: Click on the comparison field to select the desired conditional operation. 00:42: Click on the second value that you want to check for comparison. 00:46: Fill in the text box with the value that you want to compare. 00:50: Save the current progress. 00:53: Create a new branch in the step and repeat the whole process. 00:58: Celexa Branch step in your editor. 01:01: Click on the name to rename it to something meaningful. 01:05: You can now add actions in each branch, based on the conditions that you have set 01:09: up. 01:10: This guy covered. The detailed steps required to perform branching in the 01:14: karigon workflow.

 

1. Add the Branch Logic Step

  • Open your workflow editor.

  • Click the + icon to add a new step.

  • Navigate to the "Logic" tab.

  • Select the "Branch" action.

2. Configure Branches

  • Click on the "Branch" step in the editor.

  • Rename the branch paths to something meaningful. Example: "Male", "Female", "Other".

Add Conditions to Branches

  • Click "If condition is true then..." to start configuring a condition.

  • Click "Add Condition".

  • Value 1: Map the variable you want to evaluate.

  • Comparison: Choose a comparison operator.

    • Example: equals, does not equal, contains, starts with, etc.

  • Value 2: Enter the value you want to compare against. Example: "Male".

  • Click "Save" to apply the condition.

3. Add More Branches if Needed

  • Click "Add New Branch" to create additional paths.

  • Repeat the process of adding conditions for each branch.

4. Rename the Branch Step

  • Click on the title of the Branch step and rename it to clearly indicate its purpose.

5. Add Actions Under Each Branch

  • Based on the logic paths, add the relevant actions under each branch.

  • Example:

    • Male: Send a custom message.

    • Female: Assign a different set of actions.

    • Default: Handle cases that don’t match any specific criteria.

Available Comparison Operators

Operator Explanation
is true Checks if a value is true
is false Checks if a value is false
is null Checks if a value is null
is not null Checks if a value is not null
is empty Checks if an array is empty
is not empty Checks if an array is not empty
equals Checks if two values are equal
does not equal Checks if two values are not equal
greater than Checks if a value is greater
greater than or equal Checks if a value is >= another
less than Checks if a value is less
less than or equal Checks if a value is <= another
starts with Checks if a string starts with value
does not start with Checks if a string doesn't start with value
contains Checks if a string contains value
does not contain Checks if a string doesn’t contain value

 

Example Use Case:

  • Check the patient’s gender and perform actions accordingly:

    • If gender = Male, trigger a notification for a male-specific program.

    • If gender = Female, schedule a follow-up for a female wellness program.

    • Else, send a general message.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section