Multi-branch Selector Node

Definition

The Multi-branch Selector node is used to match different conditions based on the value of an input variable and route the Workflow to the corresponding branch.

This node does not call AI capabilities nor perform semantic judgment; it matches strictly according to the configured rules.

For example:

• Case 1: status = success
• Case 2: status = failed
• Case 3: status = pending
• Default: other cases

When the value of the input Variable/Var satisfies a Case condition, the Workflow will enter the corresponding branch; if none of the Cases are met, it will enter the Default branch as a fallback path.

Example Scenario

Suppose the subsequent process is determined based on the order status:

For example:

• Case 1: order_status = paid → enter the shipping process
• Case 2: order_status = unpaid → enter the payment reminder process
• Case 3: order_status = refunded → enter the refund confirmation process
• Default: enter the abnormal order handling process

Summary

The Multi-branch Selector node is suitable for handling flow branching with clear rules and explicit conditions.

If you need to route to different paths based on the exact value of a Variable/Var, use the Multi-branch Selector node; if you need to understand user intent based on natural language, it is more appropriate to use the Question Classifier node.

Frequently Asked Questions

Q1: What is the difference between a multi-branch node and a Multi branch Selector node?

• Multi-Branch Selector Node
  Evaluates all branch conditions in parallel, with no priority order. Can match single or multiple branches simultaneously (requires configuration). Function Principle: Multi-way classification (e.g., order sorting).
• IF/ELSE Node
  Evaluates in order of conditions; jumps on the first match. Only one path is selected.