Merging contacts does not fire webhooks for properties that are changed

nickgoloborodko
Contributor

We use webhooks to keep data in sync with our internal ERP system.

Looks like if two contact are merged - the webhooks are not fired for the contact that is merged to.

This causes us a lot of headaches with data going out of sync. When will this be resolved and what are the current workarounds?

Thanks,
Nick

7 Replies 7
Derek_Gervais
HubSpot Employee

Hi @nick-goloborodko,

I'm not entirely sure if this is working as designed or not; I know that we exclude contact merges from triggering certain functionality to avoid certain things like erroneous workflow enrollments. let me dig into this with my team; I'll update this thread when I have more info.

0 Upvotes
BradHarder
Member

Is there any update on this?

We have some data that exists externally that requires updating when companies are merged, and there doesn't appear to be any webhook triggers available to create. It also doesn't seem to fire any of the "update" triggers that I have set for fields.

0 Upvotes
GavL89
Member

I'm having the same issue as well, we have external systems which rely on data being associated to company and contact ids in hubspot, the web hooks are not triggered on a merge and so the data in our systems becomes orphaned.

0 Upvotes
cbisnett
Participant

Not only is there no way to subscribe to a merge event, but merging doesn't trigger a deleted event either. So when merging two companies the secondary company is deleted but there is no event.

 

Even if a merge subscription is not added is it possible to at least trigger a deleted webhook for the company or contact that is deleted during the merge? With this I think we could work around not having a merge event and try to resolve the data through the API. Without it, we're left with corrupt data that we only identify as bad when we try to use the API in the future.

0 Upvotes
phil_swelly
Participant

any update from HubSpot on that?

 

Or any workaround?

Dedupely
Contributor

To say that this is massively important for our (common) customers is an understatement. We need this functionality. Otherwise we need to do workarounds that make customers less happy with the solution and takes large amounts of time out of our schedules.

 

Any way I can push this up the dev team's priority list?

GARDUIN
Participant

Any update on this issue please ?