07 · logic
Multi-way router — named outputs for sales, support, fallback, etc.
When to use it
When one field picks among several destinations. Use fallbackOutput so unknown values still land somewhere safe.
Writeup
Multi-way router — named outputs for sales, support, fallback, etc. When one field picks among several destinations. Use fallbackOutput so unknown values still land somewhere safe.
Step by step — how to wire it
01
Normalize first
Set intent/email on a clean $json shape before Switch.
02
Add Switch rules
Rule: {{$json.intent}} equals sales → output sales. Another for support.
03
Enable fallback
Send unmatched items to a Slack “unrouted” path instead of dropping them.
04
One destination per output
sales → HubSpot, support → Linear, fallback → Slack claim.
How it functions
Rules
Each rule is a condition + optional output name (sales, support).
Fallback
fallbackOutput: extra (or similar) catches anything that matched no rule.
Used for
Used for 1
Intent-based CRM routing
Used for 2
Event-type handlers from one webhook
Used for 3
Country / plan / tier fan-out
Tips
Rename outputs so the canvas reads like a diagram.
Keep rule values lowercase and documented for form authors.