Switch Node

Switch Node

Module ID: ion.action.switch

The Switch node routes data to multiple outputs based on configurable rules or expressions. Unlike Condition (binary), Switch supports any number of output paths.

---

Overview

Use the Switch node when you need to route data to different branches based on complex logic. It supports two modes:

• Rules mode: Visual rule builder with multiple conditions per rule
• Expression mode: Custom expression evaluation

---

Handles

Input

Handle	Description
input	Data to evaluate

Outputs

Handle	Description
[rule_name]	Dynamic output for each configured rule
default	No rules matched
error	Invalid configuration or evaluation error

Tip

The Switch node has dynamic outputs - each rule you configure creates a new output handle.

---

Configuration

// node.data structure
{
  mode: "rules" | "expression",
  data: RulesData | ExpressionData
}

Rules Mode

{
  mode: "rules",
  data: {
    rules: [
      {
        name: string,           // Output handle name
        conditions: Condition[] // Conditions to evaluate
      }
    ]
  }
}

Expression Mode

{
  mode: "expression",
  data: {
    expression: string  // Expression to evaluate
  }
}

---

Example: Rules Mode

Route orders by status:

{
  "mode": "rules",
  "data": {
    "rules": [
      {
        "name": "pending",
        "conditions": [
          { "field": "status", "operator": "is_equal", "value": "pending" }
        ]
      },
      {
        "name": "shipped",
        "conditions": [
          { "field": "status", "operator": "is_equal", "value": "shipped" }
        ]
      },
      {
        "name": "cancelled",
        "conditions": [
          { "field": "status", "operator": "is_equal", "value": "cancelled" }
        ]
      }
    ]
  }
}

This creates outputs: pending, shipped, cancelled, default, error

---

Visual Representation

                    ┌── pending ──→ [Process Pending]
                    │
[Input] → [Switch] ─┼── shipped ──→ [Track Shipment]
                    │
                    ├── cancelled ─→ [Refund]
                    │
                    └── default ──→ [Unknown Status]

---

Behavior

1. Receives input data
2. Parses configuration (mode + data)
3. Based on mode:
   • Rules: Evaluates each rule’s conditions in order
   • Expression: Evaluates the expression
4. Routes to matching rule’s output handle
5. If no match → routes to default
6. On error → routes to error

---

Common Patterns

Order Fulfillment Router

[New Order] → [Switch by fulfillment_type]
                ├── pickup → [Prepare for Pickup]
                ├── delivery → [Schedule Delivery]
                ├── shipping → [Create Shipment]
                └── default → [Manual Review]

Priority Handler

[Support Ticket] → [Switch by priority]
                    ├── critical → [Page On-Call]
                    ├── high → [Assign Senior]
                    ├── medium → [Add to Queue]
                    └── low → [Auto-Response]

---

Error Cases

Error	Cause
”Not configured node”	node.data is null
”Invalid data type”	Configuration format incorrect
”Invalid switch node mode”	Mode is not “rules” or “expression”

---

See Also

• Condition Node - For simple if/else logic
• Flow Nodes Overview