Getting an Error even when I put "True" as "consider a success" - zap being stopped every time

  • 18 January 2021
  • 5 replies



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:


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

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Userlevel 7
Badge +14

Hi @KaBoom Coaching


A possible solution, check out the Zapier Manager app, which has these relevant triggers/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:

Userlevel 7
Badge +14

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

Userlevel 7
Badge +14

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.

Userlevel 7
Badge +10

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