Issue: Existing HubSpot Contacts Are Not Being Updated Through Airtable Sync
We are currently facing an issue with the Airtable–HubSpot contact sync.
The expected behavior is that when a contact already exists in HubSpot and the same contact is subsequently added to Airtable, the sync should identify the existing HubSpot contact and update its mapped properties/fields rather than attempting to create a new contact.
However, the current behavior is that when the Airtable record is synced, HubSpot identifies that the contact already exists and returns an “Contact already exists in HubSpot” error. As a result, the Airtable record is not being properly synced with the existing HubSpot contact, and the updated field values are not reflected in HubSpot.
Expected Behavior
If a contact exists in both systems, the sync should:
-
Identify the matching contact using the configured unique identifier (e.g., email).
-
Match the Airtable record with the existing HubSpot contact.
-
Update the relevant mapped HubSpot properties with the values from Airtable.
-
Avoid creating a duplicate contact.
-
Continue to maintain two-way synchronization for future updates made in either system.
Current Behavior
-
Contact is created in HubSpot.
-
The same contact is then added to Airtable.
-
During synchronization, the system detects that the contact already exists in HubSpot.
-
Instead of matching and updating the existing record, the sync fails with a “Contact already exists in HubSpot” error.
-
The Airtable data is therefore not being properly synchronized/updated in the existing HubSpot contact.
Required Action
Please investigate the record-matching and sync configuration between Airtable and HubSpot and ensure that existing contacts are correctly matched and updated rather than being treated as new records.
The sync should support updating existing HubSpot contacts when a corresponding Airtable record is created or updated, while preventing duplicate contact creation.
