CRM

Auto-merge duplicate HubSpot contacts on creation

When a new HubSpot contact is created, it searches for existing duplicates by email and normalized name.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew HubSpot contact createdHubSpotHubSpot
  • ActionSearch HubSpot for matching candidatesHubSpotHubSpot
  • LogicScore match confidence by email/phone/name
  • LogicBranch: high-confidence vs borderline
  • ActionAuto-merge high-confidence pair in HubSpotHubSpotHubSpot
  • OutputPost borderline pairs to Slack for reviewSlack

What it does

Catches duplicate contacts the moment they enter HubSpot. On every new contact, it looks for existing records that share an email, phone, or normalized name, scores the match, and either merges automatically or asks a human when the call is close.

When to use it

Run this if web forms, imports, and sales reps keep creating the same person twice and you want dedup to happen at the source instead of in a monthly cleanup. Best when you trust email as a strong identity signal but still want eyes on fuzzy name-only matches.

How it works

  1. 1A new contact created in HubSpot fires the trigger.
  2. 2Search HubSpot for candidate records matching email, phone, or normalized first+last name.
  3. 3Score each candidate: exact email match scores high, name-only match scores low.
  4. 4Branch on the score — high-confidence matches go to auto-merge, borderline ones go to review.
  5. 5Call HubSpot merge, keeping the older record as primary and filling blank fields from the duplicate.
  6. 6Post ambiguous pairs to Slack with both records and Merge/Keep buttons for a human.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.