Switch 9000 icon

Switch 9000

Switch node with more outputs.

Switch 9000

AI-generated

Overview

The Switch 9000 node is an advanced switch/router for n8n workflows, allowing you to direct data through multiple outputs based on flexible routing logic. It supports two modes: Sender (which decides how to route items) and Receiver (which receives routed items based on a specified index). This node is particularly useful in scenarios where workflow branching depends on complex conditions, such as:

  • Routing items to different branches based on field values (e.g., status, type, date).
  • Implementing multi-way switches with more than the standard two outputs.
  • Creating dynamic, rule-based flows that can handle numbers, strings, booleans, or dates.

Practical examples:

  • Route support tickets to different teams based on priority and creation date.
  • Send orders to different fulfillment centers depending on region and order value.
  • Filter incoming data streams into separate processing pipelines.

Properties

Name Type Meaning
Node Mode options Selects whether the node acts as a "Sender" (routes data) or "Receiver" (receives routed data).
Route Index number (Receiver mode only) The index of the route this receiver listens to.
Mode options (Sender mode only) Chooses between "Expression" (direct output index) or "Rules" (conditional routing).
Output number (Sender + Expression mode) The output index to which data should be sent.
Data Type options (Sender + Rules mode) The type of data ("Boolean", "Date & Time", "Number", "String") used for routing.
Value 1 boolean/dateTime/number/string (Sender + Rules mode) The first value to compare in routing rules.
Routing Rules fixedCollection (Sender + Rules mode) List of rules defining operations, comparison values, and output indices.
Fallback Output number (Sender + Rules mode) Output index for items not matching any rule.

Note:

  • The available properties depend on the selected Node Mode and Mode.
  • Routing Rules are context-sensitive and change according to the selected Data Type.

Output

Sender Mode

  • Each input item is output with a modified json structure:
    {
  "route": <outputIndex>,
  "data": <originalItemJson>
}
  • If an error occurs and "Continue On Fail" is enabled, the output will be:
    {
  "error": "<error message>"
}

Receiver Mode

  • Outputs only those items whose json.route matches the configured Route Index.
  • The output restores the original data under json:
    {
  ...<originalItemJson>
}
  • Binary data is preserved if present.

Dependencies

  • No external services or API keys required.
  • No special n8n configuration or environment variables needed.

Troubleshooting

Common Issues:

  • Invalid Output Index:
    Error: The ouput X is not allowed. It has to be between 0 and over 9000!
    Resolution: Ensure all output indices are non-negative integers.

  • Invalid DateTime:
    Error: The value "..." is not a valid DateTime.
    Resolution: Check that all date/time values are valid ISO strings, timestamps, or Date objects.

  • No Matching Rule:
    Items not matching any rule are sent to the Fallback Output (if set), otherwise may be dropped.

  • Incorrect Property Visibility:
    Some properties only appear for certain combinations of Node Mode, Mode, and Data Type.

Links and References

Discussion