Connector Improvement: Ensure metadata is updated for HubSpot Merged Companies (and Contacts?)
Answered
Our team encountered a limitation in the HubSpot connector: when two HubSpot company records merge, their metadata changes in HubSpot (e.g., is_deleted = True), but Fivetran doesn't sync these changes to the destination. A full table refresh reveals their updated metadata properties (e.g., deleted status and hs_merged_object_ids, which lists the other merged company records).
This poses a challenge for our automated process to update HubSpot companies. Many of these companies have corresponding records in our app, and we include unique identifiers as custom properties in HubSpot. However, during a merge event, when we issue a batch of updates, some records attempt to update a deleted HubSpot company.
This business use case is just the beginning. As we expand our HubSpot data in our data warehouse, similar processes will rely on identifying HubSpot companies by ID.
-
Official comment
Hi Andrew,
Sadie from the PM team here. Thanks for submitting this FR and providing a detailed description. Can you share a bit more about your automated processes that rely on this data being updated?
"Some records attempt to update a deleted HubSpot company." Sounds like your automated processes use the data synced to your destination to submit updates to the HubSpot application. Therefore, if Fivetran doesn't update that a company was deleted (via a merge event), you will assume it is not deleted and attempt to update it in the HubSpot app? Let me know if I've got that right.
Best,
Sadie
Please sign in to leave a comment.
Comments
1 comment