@kapa.ai When trying to send data to contacts in HubSpot, I'm getting an error

Warning from destination: Invalid response with status code 409 while starting ingestion: {"status":"error","message":"Contact already exists. Existing ID: id_1","correlationId":"****","category":"CONFLICT"}

It's the case for those hubspot contacts that have more than one email, and when both emails are sent in separate records for upserting. Has anybody else found this problem? Is there a fix going on?

The knowledge sources don’t mention this specific 409 “Contact already exists” conflict behavior for the HubSpot destination when multiple records refer to the same contact via different emails, so I can’t confirm an official bug or ongoing fix. From the docs, the HubSpot destination: - Uses email as the matching key for CONTACT objects (upsert on email). [[HubSpot destination](https://docs.airbyte.com/integrations/destinations/hubspot#supported-objects)] - Other objects require a unique-value property, but CONTACT is special and always keyed by email. [[HubSpot limits](https://docs.airbyte.com/integrations/destinations/hubspot#limitations--troubleshooting)] Given that: - If a single HubSpot contact has multiple emails, and you send separate records with different emails that both map to that same contact, HubSpot’s own API can respond with a 409 conflict when it detects you’re trying to create a “new” contact that actually already exists under another email. - The docs do not describe any built‑in handling or workaround for this multi‑email scenario in the destination connector. Because the knowledge sources don’t document this case, they also don’t mention any in‑progress fix or configuration option to change the matching key away from email. What you can do (based only on the docs): - Ensure that for CONTACT upserts you send only the primary email that HubSpot uses as the unique key, not secondary emails, so that each logical contact is represented by a single email in your Airbyte output. [[HubSpot destination](https://docs.airbyte.com/integrations/destinations/hubspot#supported-objects)] - If you need to store multiple emails, you may need to consolidate them into non‑key properties on a single record before sending them to HubSpot (this behavior is not documented, but it follows from the fact that only

email

is used as the matching key). Since there’s no explicit mention of this 409 issue or a fix in the provided sources, the best next step is to open or follow a GitHub issue on

destination-hubspot

with your logs and example payloads so the team can confirm whether this is a connector bug or a HubSpot API limitation.