Switch

​

When To Use

• Route by event type to different remediation paths.
• Choose notification channel based on severity class.

​

Configuration Checklist

1. Define a source value to evaluate.
2. Add cases for expected values and a default branch.
3. Connect each case to the corresponding action path.
4. Keep case values mutually exclusive when possible.

​

Inputs

• node.data metadata (uiId, componentId) and condition-specific operands/operators.
• Context values from trigger/action outputs to evaluate.
• Optional array/object inputs depending on the condition type.

​

Outputs

• Routes execution through true and false branches.
• Optionally emits evaluation details for debugging (implementation-dependent).
• Determines which downstream path executes next.

​

Failure Modes

• Missing operand values or invalid operator selection.
• Data type mismatches (for example string vs number vs date).
• Misconfigured complex expressions (switch/logical group cases).
• Unconnected branches creating dead-end workflow paths.

​

Best Practices

• Connect this where branching is required and make sure downstream edges use true/false handles.
• Always wire both branches to avoid dead ends in production runs.