Switch Node

Key Capabilities

• Supports any number of cases — configure as many output ports as your business logic requires, each mapping a string value to a named port.
• Optional default port acts as a catch-all when no configured case matches the expression result.
• Expression evaluation uses the same IExpressionEvaluator engine as the If Condition node — full access to $var, $ctx, $input directives.
• String-based case matching is case-sensitive by default, ensuring predictable routing based on exact value comparison.
• Replaces complex chains of If Condition nodes with a single, readable Switch configuration — keeping the workflow graph clean and maintainable.
• Each case's port name can be anything — use descriptive names like pending, approved, uk_region for self-documenting workflows.

Business Benefits

Business processes frequently branch into more than two paths. An order might have four possible statuses — pending, approved, rejected, or shipped — each requiring a completely different set of downstream actions. Using chained If Condition nodes for this creates a deeply nested, hard-to-read workflow graph. The Switch node solves this with a flat, parallel case structure that maps each possible value directly to the appropriate output path.

When business rules change — such as adding a new order status or a new customer region — the Switch node makes updates straightforward. Add a new case entry to the configuration and connect its port to the new handling nodes. No existing cases are affected, reducing the risk of regressions when extending workflow logic.

The default port provides a safety net for unexpected values. Rather than silently ignoring unrecognised cases, you can route them to a dedicated error-handling or logging path. This is especially valuable when the expression evaluates data from external systems where new enumeration values might be introduced without notice.

Teams that migrate from chained If nodes to Switch nodes consistently report shorter workflow definition files, easier peer review of business logic, and faster onboarding for new developers who need to understand the routing logic.

Use Cases

In This Guide