Webhook triggering only on a specific field change

Hello all,

Is it possible to have a webhook which triggers only on a specific field change?

I've tried with Zapier, Make/Integromat and n8n, but as the webhook triggers on any update on any deal, it quickly uses all my credits in Zapier/make/n8n

The first step in my automation is to check if the specific field I'm interested in has changed. The problem is that the workflow has been triggered already and the credit used, even if the workflow does nothing.

It would be great to be able to choose on which field update the webhook triggers

Regards

Tagged:

Answers

  • You can compare the previous and current values of the specific field to add a condition in Make/Integromat.

  • Josh Buesking
    Josh Buesking Member Posts: 175
    First Anniversary First Comment First Answer 5 Likes

    You still get a single operation used in make. Which does add up if you bulk update manually or update several fields via api, each field causes webhook to be sent.

    You can create a custom module in make that only triggers by certain fields or you can use something like hookdeck to filter your webhooks.

  • Raphaël HUCK
    Raphaël HUCK Member Posts: 4
    Name Dropper First Comment Photogenic

    I've tried with Zapier, Make/Integromat and n8n, and yes my first step is to compare the previous and current values of the specific field.

    However, as the workflow is triggered, it uses 1 credit / operation on each trigger. Which is more than 100 000 a month as it triggers when ANY field on ANY deal is updated

    The solution I think would be to filter on Pipedrive side before the webhook is triggered

  • If only Pipedrive added Webhooks as Actions in Automation, like FreshSales does.

  • Raphaël HUCK
    Raphaël HUCK Member Posts: 4
    Name Dropper First Comment Photogenic

    Just following up to say that I've found a solution thanks to https://hookdeck.com/ !

    I've set up the following filter:

    {
      "$and": [
        {
          "current": {
            "bfeb82d000d934d1b650a283f84556884ba01139": {
              "$neq": {
                "$ref": "previous['bfeb82d000d934d1b650a283f84556884ba01139']"
              }
            }
          }
        },
        {
          "current": {
            "bfeb82d000d934d1b650a283f84556884ba01139": {
              "$neq": null
            }
          }
        }
      ]
    }
    


    bfeb82d000d934d1b650a283f84556884ba01139
    

    being the ID of the Pipedrive custom field I'd like to monitor for changes

    Thanks to the help from Alexandre Bouchard from Hookdeck on their Slack channel

    They've been very helpful and quick to help, I highly recommend Hookdeck !

    On n8n I had to replace the Pipedrive trigger by the Webhook trigger

    Hope it can help other people :)

  • Josh Buesking
    Josh Buesking Member Posts: 175
    First Anniversary First Comment First Answer 5 Likes

    Hook Deck is a very handy tool for filtering. Solved same issue I was having.

  • Manuel Oliveira
    Manuel Oliveira Admin Posts: 1,052 COMMUNITY MANAGER
    First Anniversary 5 Likes First Comment First Answer

    Hi everyone, there's a new update that adds webhooks to automations! You can find out more here