Webhooks fired when certain fields are updated

Hi, Pipedrive is our leading CRM module. New Customers will be created here and via a webhook created in other modules. But, when adding a new deal, email note etc , this webhook will be fired also for already existing customers. A lot of unnecessary webhooks will be created. Is it possible that when only certain fields are updated or inserted (for example, an address) that this webhook will be fired? Thanks in advance, Mark.

1 Like

Hey Mark,

Unfortunately not as specific fields aren’t supported Objects. The only possible choices now would be what is listed:
activity
activityType
deal
note
organization
person
pipeline
product
stage
user

It would be possible to filter based on fields on your end though. So the web hook would still fire every time, but you’d have an if statement on your end looking at the new payload and the previous payload and check if the fields you’re interested in have changed or not. And then act accordingly.

3 Likes

Hi, I have same usage here, and get a lot of unnecessary webhooks triggered (yes, I set a filter on my end).
We have 20+ active users, and webhooks are firered more and more… and pricing plan for endpoint SaaS solution (Flow, Zapier, …) are often based on limited/ranged trigger number.
That’s the problem…

You could add a new webhook event (ie : “modified”) to differentiate between “updated” (all person fields) and “modified” contact fields (email, phone, name, … excluding read-only fields).

Noted. We’ll see what we can do.

Hi @David, is there any news on this?

I experience the same problem as loads of webhook calls are being made for updated.deal event, for monitoring just 1 custom field of deals that only triggers 10 times a month.

An idea that’s would help a lot is adding a piece of metadata to identify which field triggered the update.

Especially useful for Zapier users, since the first filter step is free so even if there are many webhook calls made, only the ones I’m looking for starts counting for the limited tasks available in the plan which is fine.

Do you know if something like this is on the roadmap?

Cheers,
Mark

1 Like

Hi @David , is there any news on this front?

We also use Zapier and this would help us immensely

Hi,

I am having the same issues. Is this any further up the list?

Thanks,

Hi, it is definitely the must have option…

@YLinfodom I have the same issue, 99% of the payloads are waste which costs me money to filter on my side.

@David we still want this, pretty please! Or just simply add an action to workflow automation called “Trigger Webhook” then we can use conditions to filter down to the fields we want to watch.

1 Like

Moving this topic to #feedback for broader attention. Keeping the thread open - Please do share your use case and impact.

In the interim, you might find some useful info here :point_down: