Rate this feature
Included in the Sept. 2022 release In Flow builder (Tools > Flow builder), you can now add branching to your flows. Branching decreases your effort to build a flow that has complicated steps with multiple applications or endpoints. For example, you might want to export data from a source application, split/branch the exported data into many different parts, and then import each part into a different destination application or lookup for processing. You can do this by adding branching, rather than building multiple flows. With branching, you are no longer restricted to a linear flow; instead, you can plan and create a flow with many branchings to solve your business problems.
Note: Flow branching does not affect any existing flows.
- Branching view options
- Branching basics
- Branching type
In the lower-left corner of the Flow builder canvas, different view icons are available. You can click an option/icon based on how you want to view your flow branching or flow at any point in time.
Select view options
The Flow builder canvas supports scrolling, so you can move through your flow horizontally and vertically. This is useful to view large or complicated flows with branching.
You can monitor your flow branching by clicking Dashboard in the left navigation menu.
After you sign in to integrator.io, select Flow Builder (Tools > Flow Builder) and click the plus sign (+) in the Destinations & Lookups canvas in the new flow. Or, you can click the plus sign (+) before or after a flow step in an existing flow.
You can then select Add branching and configure the branching type and branches as required.
Add branching to a flow
After you add a branching, you can see the branching router () icon (1) as shown below. (You can click this icon to edit the branching at any time.) The text below the router icon indicates the type of branching (2). Each dotted line represents a branch (3 & 4).
Note: The branch name (for example, Branch 1.0) is shown above the first step bubble but it represents the dotted line; a branch could include several step bubbles based on the workflow.
When you add a branching, you must specify:
You must choose the branching type based on how you want data or records to match branch conditions and flow through branches. Choose either of these options:
In this branching type, the order of branches is important because records are matched with the branch conditions sequentially based on the branch index (the order of branches). A record flows through only the first matching branch.
This example shows customer request records flow through the first matching branch based on the customer type which can be subscription tier 1, tier 2, or tier 3.
- Records that match "tier 1" flow through the "L1 support" branch.
- Records that match "tier 2" flow through the "L2 support" branch.
- Records that match "tier 3" flow through the "L3 support" branch.
Records flow through the first matching branch and can be further processed based on the workflow.
In this branching type, the order of branches is not important because records are matched with the branch conditions in parallel. A record flows through all matching branches, that is, a record flows through more than one branch.
This example shows the inventory data for three different products flow through all matching branches based on the name which can be product A, product B, or product C.
- Records that match "Product A" flow through "Store 1", "Store 2", "Store 3", and "Store 4" branches.
- Records that match "Product B" flow through "Store 2", "Store 3", and "Store 4" branches
- Records that match "Product C" flow through "Store 3" and "Store 4" branches
- All records flow through the "Store 4" branch if no conditions are defined.
Records flow through all matching branches and can be further processed based on the workflow.
You must add branches and configure conditions based on how you want to separate the data into different parts for further processing.
- Add branches based on the multiple paths that you want records to flow through. When you open the Add branching window, two branches with the names Branch 1.0 and Branch 1.1 are automatically included. We recommend changing these default branch names based on the type of branching, the conditions you’ve configured, and your flow.
- Configure conditions based on the records that must flow through each branch for further processing.
Note: If you don’t define any conditions for a branch, it’s considered an empty branch and all the records will pass through the branch.
You can configure conditions using either option:
For more information, see Manage flow branching.