Problem
Action Flow branching today supports only a binary split: If condition is met / Else.
When a value can be one of many options (for example channel, brand, group, status, or any categorical field), there is no native way to route the flow into N paths in a single step.
Current workaround
We nest multiple Branch steps under each Else path (if A → … else if B → … else if C → …). This works, but it quickly becomes hard to read, maintain, and review—especially as the number of cases grows. It also increases the risk of configuration mistakes and makes simple process changes expensive.
Requested improvement
Add a multi-way branch step (switch / case), for example:
- Evaluate one variable once
- Define multiple cases (value equals A, B, C, …)
- Provide a default / else path
Ideal extras (nice to have):
- Match operators beyond exact equals (contains, is one of, is empty)
- Reusable case labels for clarity in the canvas
- Clear validation when cases overlap or a default is missing
Why it matters
Many real support processes are categorical (“for each X, do Y”), not binary. A native multi-way branch would reduce nesting, improve readability of production flows, and make Action Builder closer to how teams already model these processes.
Expected benefit
Cleaner flows, fewer nested branches, faster edits, and lower maintenance cost for automations with multiple mutually exclusive paths.
