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.

  • Home
  • Get Help
  • How Do I
  • Getting an Error even when I put "True" as "consider a success" - zap being stopped every time

HELLO!!

 

I have a 13 step zap that integrates Stripe, Pipedrive, slack, google sheets and zapier paths :D

 

It's definitely a build I'm proud of but I'm running into a problem...

 

Here's a loom video of what I'm talking about:

https://www.loom.com/share/c9b9399b9358492daa507b8e7ac47614

 

Basically I’m getting an “error” back for something I WANT to have happen and is OKAY to have happen but since it’s an error, my zap gets turned off.

 

Please review the Loom video and let me know 🙂 Super happy to get on a video call and hash it out!

 

Thank you so much for your support <3

Hi @KaBoom Coaching

 

A possible solution, check out the Zapier Manager app, which has these relevant triggers/actions...

https://zapier.com/apps/zapier-manager/integrations#triggers-and-actions

 

 Pipedrive Zap step that results in an error:


 

Still might be a good idea to reach out to Zapier Support about this as it might be a bug: https://zapier.com/app/get-help

Alternatively, you could have 2 similar Zaps.

1 Zap that is for match found by Email, 1 Zap for match found for Name.

Then you wouldn’t need to use Paths.

@Troy Tessalone thank you!!

I’ll check out that first one!

I thought of your alternative but the problem is it would create duplicates :/ 

 

Any idea how duplicates could be avoided? :O

For the alternatives, you add a Pipedrive Deal custom field that includes the Stripe Charge ID, then include Zap step logic to search for that data point and proceed accordingly and maybe add a Delay to one of the Zaps, just a thought.

@KaBoom Coaching 
Just checking in to see if you still need help with this? 

Terms & Conditions