Loading tutorials…
Loading tutorials…
One trigger, three different downstream paths depending on data. Filters short-circuit; Routers branch. Both are FREE in Pabbly. This walks the patterns that turn one workflow into many.
Who this is forOperators with workflows that need conditional logic — different actions for different lead types, channel routing by source, status-based escalation. If you have been building 3 separate workflows that share the same trigger, you should consolidate with Router.
What you'll need
Step 1
Filter = "continue only if." Router = "branch into multiple paths." Both are Internal Tasks (free).
Filter: a single gate. If conditions are met, the workflow continues. If not, it stops. One path forward.
Router: a branch. The workflow splits into 2-N paths, each with its own conditions. Each path runs independently.
Both are Internal Tasks — they do not count against your monthly quota.
Decision rule: use Filter when there is ONE valid path and you want to reject everything else. Use Router when there are MULTIPLE valid paths and each should trigger different actions.
Step 2
Click "+" → Filter by Pabbly → set conditions. Workflow proceeds only if conditions are TRUE.
In your workflow editor, click "+" between the trigger and the first action.
Choose "Filter by Pabbly" from the action list.
In the Filter config, add one or more conditions:
- Field: pick from the data picker (e.g., Trigger → email).
- Condition: equals / contains / does not equal / is empty / etc.
- Value: the expected value (e.g., "qualified" or a specific email domain).
Multiple conditions: AND or OR logic.
Save. Send a test trigger event. If the data matches the filter, the workflow continues. If not, the workflow halts at the Filter and shows "Filter Failed" in Task History.
Step 3
Click "+" → Router → define 2-N paths, each with its own conditions and downstream actions.
Click "+" between trigger and actions.
Choose "Router by Pabbly." A multi-path UI opens.
For each path: name it (e.g., "Enterprise leads"), set conditions (e.g., "company size > 100"), and add the downstream actions specific to that path.
If multiple paths match the same record, Pabbly executes ALL matching paths. This is different from if/else — it is parallel branching.
For mutually-exclusive paths, ensure your conditions do not overlap (e.g., path 1: size > 100, path 2: size <= 100).
For "any other" cases: add a final path with no conditions (always-matches) for the default route.
Step 4
Common pattern: Trigger → Filter (reject garbage) → Router (branch valid records by type) → action(s) per path.
Real production workflows often combine both. Pattern:
1. Trigger fires.
2. Filter rejects garbage (empty email, test records, internal users).
3. Router branches valid records by type (e.g., enterprise vs SMB vs startup).
4. Each Router path has its own downstream actions (different Slack channels, different HubSpot list assignments, different email templates).
This pattern is dramatically cheaper than 3 separate workflows. One trigger, one filter, one router, three action sets = ~3 Tasks per record. Three separate workflows = 3+ Tasks AND 3x maintenance.
Step 5
Each Router path can have its own internal Filter. Add additional conditions inside a path without making the Router itself complex.
Inside a Router path, you can add additional Filter steps before downstream actions.
Example: Router path "Enterprise" → Filter "company has billing email on file" → action "create Stripe customer."
This keeps the Router logic clean (just 1-2 conditions per path) while allowing more nuanced gating within each path.
Cleaner mental model than putting all conditions in the Router.
Step 6
Manually trigger 5-10 edge-case records. Verify each takes the correct path. Catch overlapping conditions and "no path matched" silent drops.
Edge cases to test: (1) a record matching multiple paths (overlapping conditions), (2) a record matching no paths (silent drop), (3) records with empty/null values in the conditional field.
For each test, watch Task History. The execution shows which paths fired (with Path 1, Path 2, etc., labels).
If a record should match one path but matches none: tighten your default-path conditions or add a catch-all path.
If a record matches paths it should not: tighten the path conditions to be mutually exclusive.
Common mistakes
Building 3 separate workflows that share a trigger
What goes wrong: Three workflows, same Typeform trigger, each with a different downstream path. Three workflows to maintain. Three points of failure. Three workflow-name conventions to remember. 3x maintenance load.
How to avoid: Consolidate into one workflow with a Router. Each Router path replaces a separate workflow. One trigger, one place to debug, one place to monitor.
Overlapping Router path conditions
What goes wrong: Path 1: 'size > 50' and Path 2: 'size > 100.' A record with size 200 matches both — fires both paths simultaneously. Downstream actions duplicate. Double Slack message, double HubSpot update.
How to avoid: Make path conditions mutually exclusive: Path 1 "size between 50 and 100," Path 2 "size > 100." Test with edge cases.
No default/catch-all path
What goes wrong: Router has 3 paths, each with specific conditions. A record matches none of them. The record is silently dropped — no action, no notification. Months later you discover a category of records never got processed.
How to avoid: Always include a final "default" path with no conditions (always-matches) that catches everything else. Route to a manual-review queue or a default action.
Using Router when Filter would suffice
What goes wrong: You set up a Router with 2 paths, but only one path has any real actions; the other path is empty (acts as a 'reject' branch). This is confusing to read and maintain.
How to avoid: For "reject vs accept" logic, use Filter — it is cleaner. For "two different valid paths," use Router.
Mapping fields after the Router but referencing only Path-1 data
What goes wrong: Path 2 of your Router maps a field that only exists in Path 1's actions. Path 2 actions fail with 'field undefined.' Hard to debug because the workflow editor shows the field exists.
How to avoid: Inside each Router path, only reference fields from the trigger and earlier steps in THAT path. Cross-path field references do not work.
Recap
Done — what's next
How to set up multi-step workflows in Pabbly Connect
Read the next tutorial
Hand it off
Filter + Router is one of Pabbly's biggest advantages over Zapier (where every step costs Tasks). EverestX automation specialists can consolidate your existing workflow stack to cut Task usage 30-50% — typical project: $300-600 one-time + ongoing maintenance retainer.
See specialist rates
No. They are Internal Tasks — free. Only calls to external apps (HubSpot, Slack, Stripe, etc.) count against your monthly Task quota.
Router branches a workflow into multiple paths based on conditions. Iterator loops over an array of items (e.g., processing 10 line items in a single order). Different use cases — Router for branching, Iterator for batching.
No documented hard cap. Routers with 4-6 paths are common. Beyond 8 paths, consider splitting into nested Routers or separate workflows for readability.
No. Each Router path runs independently. Cross-path data sharing requires writing to a shared store (Sheets row, database) and reading back in a separate workflow.
Pabbly executes matched paths sequentially within a single execution context. From the Task History UI it looks like parallel execution because all paths complete in the same run, but internally they run in defined order.
Pabbly Connect
One trigger, three or four actions. Easy to draw, easy to break in production. This walks chaining, naming, and the error scenarios that hit on day 30.
Pabbly Connect
You bought the LTD. Six months in, you are pushing the Task ceiling and re-considering the monthly upgrade. Before paying again, run this optimization checklist — most LTD holders recover 30-50% headroom.
Pabbly Connect
Your workflow ran fine for weeks. Now it fails — or worse, succeeds but produces garbage. This is the diagnostic sequence specialists run to isolate root cause in 15-30 minutes.
Pabbly Connect
DIY Pabbly is great — until your workflow count climbs past 10 and you cannot remember what each one does. This is the honest framework: when the cost of self-managing exceeds the cost of a specialist.
Zapier
One Zap. Five different outcomes depending on the trigger payload. This is where Filter by Zapier and Paths by Zapier earn their keep — and where most DIY setups stack conditions wrong and end up routing nothing.