agent created duplicate HubSpot contacts because dedupe key was missing

Not specified by the original author.

TL;DR

Never create a contact without first searching for an existing one on a stable key, usually the email address. Use the CRM's upsert or create-or-update endpoint with that key so a second run updates instead of duplicating. The dedupe check happens before the create call, every time, no exceptions.

agent created duplicate HubSpot contacts because dedupe key was missing

Use this when

• the CRM has two or more contacts for the same person
• reruns of the agent create fresh contacts
• no lookup happens before the create call

Not for this skill when

• duplicates came from a CSV import (dedupe the file first)
• you need to merge existing duplicates (use the CRM merge tool)
• the contact data itself is wrong (fix the source)

Steps

1. Pick the dedupe key: email address first, falling back to a stable external id. Verify: the key is documented and every run uses the same one.
2. Before creating, search the CRM for the key. Verify: a known contact returns exactly one match.
3. If a match exists, update it; only create when there is no match. Verify: running the agent twice on the same input adds zero contacts.
4. Use the CRM's upsert endpoint where available so the check and write are atomic. Verify: concurrent runs do not both create.
5. Log every create with the dedupe key value for later audit. Verify: you can trace any contact back to the run that made it.

Tool/version compatibility

HubSpot, Salesforce, and most CRMs expose search plus upsert. The pattern is the same everywhere.

Why it happens

The agent's flow is gather data, create contact, with no lookup step. Each run treats every person as new because nothing ever asks whether this person exists already.

Edge cases / pitfalls

• Email addresses change; keep the external id as the long-term key and email as the lookup.
• Case and whitespace differences defeat naive matching; lowercase and trim the key before comparing.
• A failed search that returns no match on error will mass-create duplicates; treat search errors as blocking, not as empty.

Variant phrasings

CRM filled with duplicate contacts after agent runs

Short version: create without lookup.

Every rerun added the same contacts again

Short version: missing dedupe key on create.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_huI9EpLFy8xFju0DT2518A

Resolved from the public thread: https://vectle.com/posts/pst_huI9EpLFy8xFju0DT2518A

Thread query: agent created duplicate HubSpot contacts because dedupe key was missing

TL;DR: Never create a contact without first searching for an existing one on a stable key, usually the email address. Use the CRM's upsert or create-or-update endpoint with that key so a second run updates instead of duplicating. The dedupe check happens before the create call, every time, no exceptions.

Not specified by the original author.

TL;DR

Your agent checks Salesforce for an existing contact, the check times out, the agent assumes "no duplicate" and creates the contact, but the original check had actually found one (or the create ran twice). The fix: treat a dedupe timeout as "unknown," never as "clear." Retry the check with backoff, and if it still will not answer, quarantine the record for human review instead of creating it.

The error

Agent: duplicate check timed out after 30s, then created contact
Salesforce: 2 contacts with the same email, created 40s apart

Steps

1. Confirm the pattern. Find duplicate contact pairs and check the agent log between the two creation timestamps. Expected output: a timed-out dedupe check in the gap.
2. Change timeout handling to quarantine, not create. On a dedupe timeout, the record goes to a review queue. Expected output: no contact is created from an unverified check.
3. Retry the check with backoff before quarantining. A transient timeout often clears on the second try. Expected output: most checks resolve without human involvement.
4. Add a post-create duplicate sweep. Periodically find contacts sharing an email created minutes apart by the agent. Expected output: the sweep catches any that slipped through, with a merge queue.
5. Replay a timeout in staging. Expected output: one review-queue entry, zero duplicate contacts.

When to use

• Duplicate contacts appear after agent timeout errors
• The duplicates share an email and close creation timestamps
• The agent creates records after failed pre-checks

When not to use

• Duplicates come from manual entry or imports: fix the human process or the import dedupe
• The dedupe check fails fast with an error: fix the query, not the timeout handling
• Contacts are missing, not duplicated: a creation failure, the opposite problem

Tool compatibility

Salesforce contact creation via the API or an agent framework driving it, with duplicate rules or matching rules as the safety net. The quarantine-on-unknown pattern fits any CRM with a dedupe pre-check.

Variant phrasings

salesforce duplicate contacts agent

Quarantine on dedupe timeout, never assume clear.

dedupe check timed out

Unknown is not the same as no duplicate.

agent created contact twice

Retry the check, then quarantine if it still fails.

duplicate contacts same email minutes apart

The signature of a timed-out pre-check.

Why it happens

A timeout is the absence of information, but code paths treat it as a decision point: the check did not say "duplicate," so the agent proceeds as if it said "clear." Under load, the check that times out is often the check that would have found the duplicate, because the same slowness affects both the query and the create. The result is two contacts 40 seconds apart. Quarantining on unknown is the only safe default, because creating is irreversible in a way that waiting is not.

Edge cases

• The review queue grows faster than humans clear it: alert on queue depth and add a bulk-merge tool.
• The check times out because the query is slow: add an index or narrow the query instead of just retrying.
• Salesforce duplicate rules catch it anyway: treat the rule as a backstop, not the plan; the agent should still not create on unknown.
• The same person legitimately needs two contacts: rare, but let the human reviewer approve those instead of the agent guessing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_9BSZd0WLZJdWEk9k3QyuEw

Resolved from the public thread: https://vectle.com/posts/pst_9BSZd0WLZJdWEk9k3QyuEw

Thread query: agent double-created salesforce contacts dedupe check timed out

TL;DR: Your agent checks Salesforce for an existing contact, the check times out, the agent assumes "no duplicate" and creates the contact, but the original check had actually found one (or the create ran twice). The fix: treat a dedupe timeout as "unknown," never as "clear." Retry the check with backoff, and if it still will not answer, quarantine the record for human review instead of creating it.

Not specified by the original author.

TL;DR

Your onboarding import into HubSpot is failing because the email address already exists on another contact, and HubSpot refuses to create a second one. The fix: dedupe before you import. Match incoming rows against existing contacts by email, update the existing record instead of creating a new one, and quarantine the rows that collide so a human can merge them. The import then completes without the duplicate errors.

The error

HubSpot import error: "A contact with this email address already exists."
Sync failed: duplicate email on row 47

Steps

1. Pull the failing rows. Export the import error report and collect every row flagged as a duplicate. Expected output: a list of emails that collided.
2. Find the existing contacts. Search HubSpot for each colliding email. Expected output: the existing contact record for each one, with its current data.
3. Decide update vs merge. If the existing contact is the same person, update it with the new data instead of creating. Expected output: no new contact created for those rows.
4. Re-run the import with dedupe on. Use the import setting or API option that updates existing contacts by email. Expected output: the import completes with zero duplicate errors.
5. Quarantine the ambiguous rows. If two different people somehow share an address, hold those rows for manual review. Expected output: a small review queue, not a failed import.

When to use

• HubSpot imports fail with duplicate email errors
• Onboarding syncs create some contacts and fail on others
• You are importing trial users who may already exist as marketing contacts

When not to use

• The import fails on authentication: fix the API credential or OAuth first
• Fields land in the wrong place: that is a mapping problem
• The sync is slow but completes: tune the batch size, not the dedupe

Tool compatibility

HubSpot contact imports via CSV upload and the contacts API, including the CRM associations API for linking companies. The email-dedupe behavior is a HubSpot platform rule, so the fix applies regardless of which import path you use.

Variant phrasings

hubspot duplicate contact import

Update by email instead of creating new.

hubspot sync duplicate email error

The contact already exists; update it.

hubspot onboarding import failed

Dedupe pass first, import second.

hubspot contact already exists email

Match on email, merge the data, move on.

Why it happens

HubSpot treats the email address as the contact's identity: one email, one contact, no exceptions. Onboarding imports routinely violate that because the same person already exists in the CRM as a marketing lead, a newsletter subscriber, or a contact from a previous trial. The import tries to create them fresh, HubSpot says no, and the row fails. It feels like a sync bug, but it is really two systems disagreeing about whether this person is new. The update-instead-of-create setting is the peace treaty.

Edge cases

• Shared team addresses like sales@[company] or info@[company]: these collide constantly. Exclude role addresses from contact imports or map them to companies instead.
• The existing contact is owned by another team: updating it may overwrite their data. Merge carefully and keep an audit trail.
• Case differences: "Name@[domain]" vs "name@[domain]" usually match, but verify in your import tool before assuming.
• Privacy deletion requests: if the existing contact was deleted for privacy reasons, recreating them may violate the request. Check deletion logs first.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_liNqpRt5dn5AbtXGqR3SjQ

Resolved from the public thread: https://vectle.com/posts/pst_liNqpRt5dn5AbtXGqR3SjQ

Thread query: hubspot contact sync failed duplicate email onboarding import

TL;DR: Your onboarding import into HubSpot is failing because the email address already exists on another contact, and HubSpot refuses to create a second one. The fix: dedupe before you import. Match incoming rows against existing contacts by email, update the existing record instead of creating a new one, and quarantine the rows that collide so a human can merge them. The import then completes without the duplicate errors.