About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Question

Piperdrive "Deal Status" trigger not working

  • 11 April 2022
  • 7 replies
  • 97 views
B

Hi

 

I’m trying to set up a zap that detects when a deal in Pipedrive is first assigned a specific Deal Status, and message a slack channel.

 

Through testing, the zap works perfect (pulls the right data and messages the slack channel), however when I turn on the zap I can’t get it to fire by updating deals in Pipedrive.

 

I’ve tried both the “Updated Deal Stage” and “Deal Matching Filter” trigger options.

 

Can anyone suggest what might be causing this to not trigger?

 

Thanks

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

7 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @blinc 

Good question.

After turning the Zap ON and testing, check your Zap Runs for possible errors: https://zapier.com/app/history/

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Troy Tessalone
Userlevel 7
Badge +14

@blinc 

Zapier had an incident that may be related per their Status Page: https://status.zapier.com/

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
A

Hi,

 

I also have the same issue, the trigger is an updated deal status (it should be instant).

When I created the zap, everything worked well. When I tried a real test into Pipedrive, the zap is not running.

I looked at the zap history and there are no zap running which is weird.

Does anyone know how solve that problem ? 

Thanks in advance.

Best

 

Troy Tessalone
Userlevel 7
Badge +14

Hi @Alexandre Legrand and @blinc 

Both Pipedrive and Zapier have had recent incidents that may be related, altho not sure.

https://status.pipedrive.com/

https://status.zapier.com/

 

May be best to open a ticket with Zapier Support: https://zapier.com/app/get-help

 

Pipedrive

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
B

Has this issue been resolved? i am having the same issue, using Updated Deal Stage In Pipedrive as the trigger, everything works well during the test when setting up however after publishing it does not trigger at all.

 

Regards,

Beau

Troy Tessalone
Userlevel 7
Badge +14

Hi @BeauWoods 

As a workaround try using this Zap trigger: Pipedrive - Deal Matching Filter

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
christina.d
Userlevel 7
Badge +9

Hi there @BeauWoods, @Alexandre Legrand, and @blinc! Thanks so much for reaching out. 

I’m sorry to hear about this! Have ya’ll had an opportunity to open a ticket with our friends in support? They should be able to dig into this for ya’ll and see what the underlying issue is. It’s certainly possible you’re being impacted by a bug and if so the team can log this for you. I’d definitely recommend linking them back to this post as well so there’s some added context.

Thanks again and definitely keep us in the loop! 

Terms & Conditions