With the Webhooks V2 BETA being announced and the mention of V1 being replaced at some point
Webhooks v2 is here to eventually replace webhooks v1. Please consider migration as soon as convenient.
I wanted to voice my concern for the many, many clients we’ve worked with who have existing setups in place that make use of V1 webhooks. The notion that at some point their workflows will stop working unless we put considerable effort in to rework them is pretty scary.
Please consider allowing the already established V1 webhooks to be grandfathered in and to continue running alongside V2. Not all of our clients (or others) are going to be willing to re-engage to rebuild automations when they’re currently working without issue.
Our clients are all using Zapier and where possible we’ve used the native Pipedrive Integration for triggers rather than webhooks, however, often webhooks are used because it’s the only viable option (e.g. only trigger upon a certain field changing, not possible with a native Zapier trigger). To rework each of their automations that use webhooks will require considerable effort from us and cost on their part.
I understand that V2 pushes fewer updates (i.e. less bandwidth and resource of PD’s end, meaning lower costs) and that maintaining two systems indefinitely isn’t cost effective. I don’t have a perfect solution but I wanted to get this discussion started.