Webhooks v2 will become the new default version
![Manuel Oliveira](https://us.v-cdn.net/6037014/uploads/userpics/JUAN4B0W3TNG/nG2RKIZFYP3TB.jpg)
![1000 Comments](https://us.v-cdn.net/6037014/uploads/badges/85AOWIAA0HRJ.png)
![250 Likes](https://us.v-cdn.net/6037014/uploads/badges/W2LBSQ0PHZZM.png)
![25 Answers](https://us.v-cdn.net/6037014/uploads/badges/AP3R9GSCWEGX.png)
![Third Anniversary](https://us.v-cdn.net/6037014/uploads/badges/SVDWMCN0ELNT.png)
What’s changing?
From March 17, 2025, all new webhooks created via API will be version 2.0 by default. Until further notice, legacy v1 webhooks can still be created by specifying the version parameter in the API request body.
Why is it changing?
We introduced webhooks v2 at the beginning of 2023 to add reliability and stability by reducing duplicate and missing webhook triggers and delays. In addition, lead webhooks are supported in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.
I'm using webhooks v1, do I need to migrate to the new version?
Yes. Webhooks v2 and v1 will continue to run in parallel for now, but v1 will be deprecated entirely before the end of 2025. Please review the v1 to v2 migration guide closely, as there are significant differences in webhooks v2’s payload.
Comments
-
Hi @pieterh Pipedrive's Zapier app is unrelated to webhooks, but our team is aware of this and is already looking into the next steps in conjunction with Zapier. There’s no date for an update yet but keep an eye out here in the community for more updates.
1 -
Thank you Manuel. As a reference: There is polling ongoing in de Zapier app that uses 90k tokens a day, even if there are no Zaps triggered. Improving that will probably help you a lot in your infrastructure challenges!
To me, it would be sensible if the Zapier app would be improved before the new API usage rules kick in. I'm wondering if anybody else has this problem?
0 -
For anybody who has too many API requests because they are using the official Pipedrive Zapier app triggers, this is causing a lot of API requests, because the Pipedrive app will poll every 2 or 5 (depending on your Zapier plan) seconds. So even if there is no zap task usage, it will take up Pipedrive API tokens.
There is a work around, but it requires you to have access to Zapier Webhooks and Pipedrive Automation. I've changed the trigger in the Zap to a webhook listener. I've then created a webhook call in Pipedrive Automation to trigger the Zap when there is a change to a pipedrive object. I made the changes yesterday just after noon. I removed to Pipedrive triggers. I'm hoping this will reduce the number of calls with about 15k tokens/trigger/day.
0 -
Tangential to this specific discussion, but anyone, please ping me if you start getting weary of using the Zapier <> Pipedrive integration for event/task sync. I'm not sure why anyone would still rely on Zapier for this when there are so many better options available for event pipelines.
Our approach - private analytics/event pipeline connected to Pipedrive:
0 -
It's one thing to deprecate and another to shut down. Are you saying creation of new v1 webhooks will cease before end of 2025 or they will be shut down completely? If the answer is to shut down completely, please reconsider as it would be too quick. V2 only recently got out of beta.
0 -
Hi @jp-apps , they will indeed shut down completely before the end of the year, but there is a transition period. If you are using webhooks v1, please plan your migration to v2 accordingly.
0