Skip to main content

Hi Community,

I’m building a lead segmentation Zap where each incoming lead from a quiz should be routed into only one group (e.g., Pregnancy, Medicare, Medicaid, Private Qualified, or Needs Review).

Originally, I designed this using Zapier Paths—with each path representing a different condition (Pregnant = Yes, Age ≥ 65, Income Tier, etc.).

However, in practice, some leads are getting assigned to multiple groups at once, even though they should logically match only one. For example, a lead might be added to:
Pregnancy + Medicare + Private Qualified + Needs Review—which should never happen.

I’ve recorded a Loom showing how the original Path structure was set up. My logic should be exclusive, but it appears Paths are not terminating the Zap or blocking other paths from running.

I’d love insight from anyone who’s built logic like this at scale.
Is there a better way to enforce exclusivity using Paths?
Or is the only safe method to stack Filters linearly (like in the final design, you’ll see in the loom)?

👉 Loom Link:

 

Hey ​@MoreHealthQuotes ,

 

I have viewed your Loom videos. You should make your filters more tighter and strict. Something is not correct setup correct that is why this is happening.

 

I will suggest hiring a Zapier Certified Expert from here who can look up for you this. 


Hi ​@MoreHealthQuotes 

NOTES:

  • Zaps will NOT skip filter steps.
  • If a Filter step does not pass, then Zap steps after the Filter step will not be tried.
  • e.g. Linear Zap would stop at Zap step 2 if the Filter conditions were not met.

 

Loom video did not show how the Path Filter conditions were configured for us to have context.

Zap Runs can process via 0+ Paths based on Filter conditions.

Help links for using Paths: https://zapier.com/apps/paths/integrations#help

 

You likely need to have stricter Filter conditions.