Switch Node
Purpose: Conditional branching based on data evaluation Switch nodes evaluate conditions and route execution to different paths.

- Input Handle
- Output Handles
Left Side - Condition InputReceives data to evaluate against conditional branches.Accepts:
- Workflow variables
- Previous node outputs
- Template expressions
- Any data for conditional evaluation
Switch nodes support dynamic branching: you can add multiple ELIF branches for complex conditional logic. Branches are evaluated in order: IF → ELIF 1 → ELIF 2 → … → ELSE.
String Matching (6 operators)
String Matching (6 operators)
string
Check if value contains substring (case-insensitive)Example:
"Hello World" contains "world" → truestring
Check if value does not contain substringExample:
"Hello World" not_contains "xyz" → truestring
Exact match comparison (case-insensitive)Example:
"admin" equals "ADMIN" → truestring
Not equal comparisonExample:
"user" not_equals "admin" → truestring
Check if value starts with prefixExample:
"Hello World" starts_with "Hello" → truestring
Check if value ends with suffixExample:
"file.pdf" ends_with ".pdf" → trueList Operations (2 operators)
List Operations (2 operators)
Empty & Boolean Checks (4 operators)
Empty & Boolean Checks (4 operators)
Unary operators (
is_empty, is_not_empty, is_true, is_false) don’t require a right operand.- AND Logic
- OR Logic
All conditions must be trueUse for: Strict validation, multiple requirement checks
- IF: First condition evaluated
- ELIF: Additional conditions (evaluated if previous failed)
- ELSE: Default path if no conditions match
- Content moderation (check for inappropriate content)
- User role routing (admin vs. user paths)
- Error handling (check for error states)
- A/B testing (route based on user segment)

