n8n - 💡(How to fix) Fix Switch node supports multiple conditions per rule, but UI does not expose this [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#30421Fetched 2026-05-14 03:45:17
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

A simple "If" node includes an "Add condition" button, where we can chain multiple conditions with AND/OR

But for a "Switch" node, the UI seems to indicate this isn't possible. Each rule can only include a single condition, and no "Add condition" button.

However, when editing workflows via n8n-mcp, I was able to get this:

<img width="703" height="1460" alt="Image" src="https://github.com/user-attachments/assets/0050bbe9-9001-4fba-ba73-87875e8e9f84" />

This runs correctly. I can edit or remove conditions from each rule, now that they were added via API. But I can't manually add conditions via the UI

To Reproduce

  1. Create a Switch node
  2. Add a routing rule
  3. Notice there is no way to chain conditions within the same rule
  4. setup n8n-mcp in an LLM, and ask it to do it instead
  5. The UI should now show both conditions, chained correctly

Expected behavior

I should be able to add conditions manually

Debug Info

Debug info

core

  • n8nVersion: 2.20.6
  • platform: npm
  • nodeJsVersion: 24.15.0
  • nodeEnv: undefined
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: ae2847cf-df28-45de-a3da-575da25c930a

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (x11; linux x86_64; rv:149.0) gecko/20100101 firefox/149.0
  • isTouchDevice: false

security

  • secureCookie: false

cluster

  • instanceCount: 1
  • versions: 2.20.6
  • instances:
    • instanceKey: 23c467b3-79a5-4569-b4c3-fb6df384f62a, hostId: main-dUJewSrp6B44DHe4, instanceType: main, instanceRole: leader, version: 2.20.6
  • checks:
    • check: hostid-clash, status: succeeded, warnings: -
    • check: lifecycle, status: succeeded, warnings: -
    • check: split-brain, status: succeeded, warnings: -
    • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-13T17:26:02.030Z

Operating System

LXC inside Proxmox

n8n Version

2.20.6

Node.js Version

24.15.0

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

I should be able to add conditions manually

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Switch node supports multiple conditions per rule, but UI does not expose this [1 comments, 2 participants]