Pipedrive Lead Creation creates 2 times (instead of 1)

[Finspro]

Hello,

i have a new issue with Lead Generation.

Workflow ID: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZiMDYzZjA0Mzc1MjY4NTUzYzUxMzAi_pc

I use Person Update trigger and filter for specific value.
Then i update the triggered field back to a non valid value.
Then i want to create a Lead for that Person.

The Lead is generated - 2 times
I even setup a delay step of 1 minute between the update of the field and the Lead generation step.
But i always get 2x Lead created.

For example last two History IDs:
IjU3NjUwNTY4MDYzNTA0Mzc1MjZhNTUzZDUxMzY1MTYzNTQzMzBmMzIi_pc
IjU3NjUwNTY4MDYzNTA0Mzc1MjZhNTUzZDUxMzY1MTYzNTQzMzBmMzEi_pc

Can you please tell me what i am doing wrong here or what is my issue?
I tested same intended workflow in Make.com and do not have an issue.

Thank you in advance.

Regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

Upon reviewing your workflow, we’ve observed that multiple POST webhooks appear to have been installed in Pipedrive. Specifically, when checking the task history, we noticed that each entry is associated with a different webhook ID — 1204576 and 1204577. This duplication is likely causing multiple trigger responses and resulting in the creation of duplicate leads.

Additionally, the trigger response in your workflow also reflects two webhook IDs, which further confirms the issue.

To resolve this, we recommend the following steps:

1. Create a new workflow from scratch.
2. While setting it up, ensure that you click the "Save & Send Test Request" button only once — multiple clicks can result in multiple webhook entries.
3. If you need to capture the response again, please use the "Recapture Webhook Response" button instead of repeating the save/send action.
4. After setting up the trigger, monitor the webhook responses in the task history, and confirm that only one webhook ID is being used.

This should help eliminate duplicate lead creation caused by multiple webhook triggers.

Please feel free to reach out if you need further assistance.

 

[Finspro]

Hi @Preeti Paryani ,

thank you for the information, will check that immediately and let you know.
One more question - do we have some kind of overview to see the "installed" webhooks per Workflow or in sum for all?
Would help a bit with the analysis and to deduplicate upfront.
Or you could manage that maybe internally to prevent duplicate entries for webhooks.

Although i have no clue how the double entry has happened, i do always the same.
But as mentioned, i will test and let you know,

Best regards
Christian

 

[Finspro]

Hi @Preeti Paryani ,

this worked as it seems. A new setup Workflow is creating only one Lead.

Could you maybe check for the both mentioned points?
- Overview of potential double webhooks in a workflow or how many are set at all?
- Preventing of double saving one from the start?

Thank you for your feedback.

BR
Christian

 

[ArshilAhmad]

Hi @Preeti Paryani ,

thank you for the information, will check that immediately and let you know.
One more question - do we have some kind of overview to see the "installed" webhooks per Workflow or in sum for all?
Would help a bit with the analysis and to deduplicate upfront.
Or you could manage that maybe internally to prevent duplicate entries for webhooks.

There is no overview that shows the installed webhooks per workflow. However, in Pipedrive, you do get the Webhook ID, which should remain the same across all Task History IDs. If it doesn't and you see different Webhook IDs across the task history, it means that two or more webhooks have been generated in the backend.

The issue occurs when a user clicks the 'Save & Send Test Request' button multiple times in POST webhook-based trigger steps, which is why we display a warning message if it is clicked more than once.

In POST webhook-related trigger steps, if you need to capture the data again, make sure to click the 'Re-Capture Webhook Response' button instead of the 'Save & Send Test Request' button.

 

[Finspro]

Hi @ArshilAhmad ,

thank you for the additional information.
Will check this next time i run into the same problem.

Have a good day!
BR
Christian