When the deal value is updated for a deal, the webhook endpoint is hit multiple times, two of which contains the deal value = 0 and one of them contains the correct updated value. Is this a feature? This is creating a problem in differenting between deals having actual value as 0 and the wrong ones generated because of this feature/bug.
Hi @techengers
Sorry for taking so long to answer your question.
If a Deal value is only being updated, the endpoint shouldn’t be hit multiple times and I just tested and wasn’t able to get the same result as you.
Have you checked the changelog on the Deal to see if there’s anything else happening? Also check to see if there’s other Webhooks that could be interfering or even automations that could be causing such problems.
Has anyone else had this happen recently?
We just started using Webhooks for updating a report and I’ve been seeing instances where we are receiving multiple HTTP requests initiated by a Webhook for deals, with the Event action setting on “*”.
The particular instance I saw today, was with a deal update where “change_source”: “app”.
Checking the “CHANGELOG” on the deal, there appears to have been only one change performed resulting in the deal value decreasing.
Both requests are obviously for the same “object”, “action”, “id” and “company_id”.
For the 2 HTTP requests, there are 2 differences:
-timestamp_micro values are different:
-The 1st request has “timestamp_micro”: 1611268213533166
-The 2nd request has “timestamp_micro”: 1611268213547010
-The 2nd request has 2 additional columns provided in the Body for the current and previous sections that are not present in the 1st request:
-“last_activity”
-“next_activity”
Seems it comes from Workflow Automation
One request has comes with
"change_source": "app",
"pipedrive_service_name": null,
Second one came with
"change_source": "automation",
"pipedrive_service_name": "automation-phpapp-proxy",