Skip to main content

Hello everyone,
I'm working on Pipedrive and I'd like to create a Zap that triggers a calculation only when certain precise values are modified. In order to optimize the use of my tasks, I'd like to apply a filter so that the Zap is only triggered when these values are actually modified.
After testing numerous configurations, I haven't managed to find the right combination: either the filter always lets the Zap through, or it systematically blocks it. Being a beginner, I wonder if some of you have already encountered this difficulty when creating a filter based on Pipedrive data received via a webhook.
Thank you in advance for your invaluable help.

Translated with DeepL.com (free version)

Hi ​@AlexN92-L 

Some app webhook payloads do not indicate the changed field or the old/new values for the changed fields.

In that case, the webhook payload only includes all of the current data about the record.

You would have to keep a log of the record data to compare a before/after for the field values to then filter.

 

One option is to use Zapier Tables as the log:

https://zapier.com/apps/zapier-tables/integrations#triggers-and-actions

https://zapier.com/apps/zapier-tables/integrations#help

 

Zap steps using Zapier Tables count as 0 Tasks in Zap Runs.


i'm going to try this thank you very much