Skip to main content
This feature only applies to Embedded iPaaS
The Branch connector works similarly to an If-Else connector, but instead of evaluating a single condition, it allows you to define multiple conditions and route data through one or more paths depending on which conditions evaluate to true. Think of it as a sequence of conditional checks that can all execute independently. Use Branch when your workflow logic needs to handle multiple outcomes or decision trees within the same step. Each branch evaluates a condition, and if the condition is met, the corresponding path executes. You can optionally define a default path to handle any data that doesn’t match your criteria.

​
Example: Accounting Workflow

Suppose you’re building an automated accounting flow that processes journal entries imported from multiple systems. You might use Branch to route entries based on their amount or account type:
  • Condition 1: If amount > 100000, send the entry to an “Approvals” workflow for manual review.
  • Condition 2: If accountType == "Revenue", push the entry to your ERP via API.
  • Condition 3: If accountType == "Expense", send it to your reporting database.
  • Default Path: Log any other entries for audit.
This setup allows multiple branches to execute simultaneously if more than one condition is true—ideal for complex decision logic that goes beyond a simple true/false evaluation.
By chaining branches together, you can handle granular business rules without writing custom code. Branch gives developers precise control over how workflows diverge and converge, making it a core logic component in Alloy’s automation engine.
⌘I