Pipedrive webhooks persist despite three consecutive days of 400 Bad Request responses.
In our application, we have an integration with Pipedrive, and we've observed that Pipedrive continues to send invalid webhooks to us. This typically happens when a customer disconnects their Pipedrive account or for other similar reasons. To address this, we return a 400 Bad Request status code to stop the webhook delivery. However, based on our observations, Pipedrive does not delete the webhook even after receiving this response for three consecutive days.
Answers
-
Hello @Akshay,
As per our retry logic, if we are unable to deliver the webhook request (by receiving a non-2XX code) for 3 consecutive days, we will delete the respective webhoo,k but if it is not working as expected for you, could you contact our support team with information like the webhook ID that should have been deleted, the account under which the webhook is created so that our team would be able to look into this further.
0