Switch

Node catalog Logic

On this page

Route to multiple branches using conditions.

Usage and specifics

Configure rules and corresponding outputs. Check type comparisons and unmatched items; connect every expected branch.

Technical type : switch. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`rules`	`array`	`[{"id":"1","label":"","combinator":"and","conditions":[{"field":"","operator":"equals","value":""}]},{"id":"2","label":"","combinator":"and","conditions":[{"field":"","operator":"equals","value":""}]}]`	-
`rules[].id`	`string`	`"1"`	-
`rules[].label`	`string`	`""`	-
`rules[].combinator`	`enum`	`"and"`	`and`, `or`
`rules[].conditions`	`array`	`[{"field":"","operator":"equals","value":""}]`	-; min 1
`rules[].conditions[].field`	`string`	`""`	-
`rules[].conditions[].operator`	`enum`	`"equals"`	`equals`, `not_equals`, `contains`, `not_contains`, `gt`, `gte`, `lt`, `lte`, `empty`, `not_empty`
`rules[].conditions[].value`	`string`	`""`	-

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "rules": [
    {
      "id": "1",
      "label": "",
      "combinator": "and",
      "conditions": [
        {
          "field": "",
          "operator": "equals",
          "value": ""
        }
      ]
    },
    {
      "id": "2",
      "label": "",
      "combinator": "and",
      "conditions": [
        {
          "field": "",
          "operator": "equals",
          "value": ""
        }
      ]
    }
  ]
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.