Breaking change in the JSON response structure of the Delete Person webhook

What?

We will be introducing a breaking change in the JSON response structure of the Delete Person webhook.

Currently the data for a Delete Person webhook is incomplete. For example, if a user has saved more than one email/phone nr on a Contact, then only the primary email/phone nr. will appear in the webhook data. Because of this, we will change the property type from a string to an array and add additional values (e.g. secondary email/phone nr) into the array when they are present.

Why?

If our customers remove a Person, they can then use webhook data to delete the same information on their end. We would like to make sure when information is removed from Pipedrive, it can also be seamlessly removed from our customers’ databases.

Who is affected?

Anyone who has set up a webhook for a Person Delete event. If you or your team has built functionality on top of a previous response structure, then please make sure your code is changed accordingly.

Published on August 23, 2019