Switch
Control FlowSend a workflow down one of several paths based on a value
Overview
The Switch node is a multi-way fork in the road. It looks at one value and compares it against up to four cases. The first case that matches wins, and only that branch runs. If nothing matches, the Default branch runs instead. Think of it as an If Condition node with more than two exits.
Switch vs If Condition
Use If Condition for a simple yes/no split. Use Switch when the same value can lead to three or more different outcomes — like routing by status, plan, or category.
Parameters
Configuration options for this node
Input ValueText Input
Required
The value to route on. This is usually a variable from an earlier step, such as an order status or a plan name.
Example:
{{ status }}OperationDropdown
Required
How the input is compared to each case — equals, contains, starts with, greater than, and more. The same comparison is used for every case.
Default:
equalCase 1 to Case 4Text Input
The value for each branch. The first case that matches the input decides which path runs. Leave a case empty to turn it off.
Example:
shippedUsage Example
Route an order by its status
Handle shipped, pending, and cancelled orders differently
Input Value:
{{ order.status }}Operation: equal
Case 1:
shipped — send a tracking emailCase 2:
pending — wait and check againCase 3:
cancelled — issue a refundDefault: log it for a human to review
Best Practices
Tip: Always connect the Default branch
Wire up the Default path so unexpected values still go somewhere sensible instead of quietly stopping the workflow.
Tip: Order matters
The first matching case wins, so put your most specific values in the earlier cases.