Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi!

I crated quite a branching logic to move incoming leads into a specific pipeline for the CRM I am using, based on UTM and tracking parameters for each submission.

I found out that Zapier tries to go trough every path, even if one paths already was successful.

I want to prevent exactly that. I recon Zapier starts with the first path and goes on to the next to the right.

 

Question:

  • Is it possible, that when a the first path was successful, to prevent it going onto the next paths?

  • For every Path successful the data entry gets a tag. I tried to use this tag for other paths as a filter, but it did not work.

  • Is there a better way to do it?

  • Additionally, I would like to have one path as a "catch all" for those who did not fit in any other path (but only then)

Thanks!!

Go to this question on Reddit

 

Hi @ee_international 

Good question.

You have to make sure the Filter conditions for each Path are mutually exclusive so only 1 Path proceeds.

Zapier will try to proceed down each Path.

It’s not possible to define the order in which Paths process, nor stop other paths from proceeding if the Path Filter conditions are also met.

Thank you for clearing this up. It would be a great feature to be able to define a order and to have a “stop zap” block.

 

Making paths mutually exclusive is very complicated in my case.

 

Is it possible to put some kind of labels to the dataset with conditions, so I can then use those labels to build my path logic in the bottom part of the zap?

This would make the setup way easier to manage and the filter part is not so much bloated with multiple “or” parts and slightly different filters.

What I have done in the past is use a python code block to run the logic I needed then used a pass/fail variable in the output. It made checking conditions a little easier. 

I prefer Python but you could do it in JavaScript. Check the logic for the condition then set a pass or fail tag.

Generally for me this was on line item properties. So if what I needed was there I would mark it would output “condition_name” with a pass value. It helped to stop some zaps failing over and might work well for you as you could set a pass or fail for each path. 


The coding isn’t that difficult and  AI can probably do most of the heavy lifting for you. If you’d like a hand just let me know.

 

@ee_international 

FYI: You can submit feedback and feature requests via a ticket to Zapier Support: https://zapier.com/app/get-help

Terms & Conditions