CRM
HubSpot Duplicate Contact Auto-Merge with Source-Trust Survivorship
Detects newly created or updated HubSpot contacts that duplicate an existing record, merges them using source-trust field-survivorship rules.
How it runs
The automated pipeline, trigger to output.
- TriggerHubSpot contact created or updatedHubSpot
- ActionSearch HubSpot for duplicate candidatesHubSpot
- LogicApply source-trust survivorship rules per field
- ActionMerge survivors and flag losers in HubSpotHubSpot
- ActionInsert field-level decisions into Postgres audit tablePostgres
- OutputPost merge summary to SlackSlack
What it does
When a HubSpot contact is created or updated, this workflow finds matching duplicates and merges them into a single surviving record. Instead of blindly overwriting, it resolves each conflicting field using a source-trust ranking (for example, Salesforce-sourced beats web-form beats manual import) and writes a complete audit row so you can prove which value won and why.
When to use it
Run this when inbound forms, list imports, and sales activity keep spawning duplicate contacts and your team wastes time hand-merging. It is ideal for ops teams that need a defensible, repeatable merge policy plus a paper trail for data-governance reviews.
How it works
- 1A HubSpot contact create/update event fires the workflow.
- 2The flow searches HubSpot for candidate duplicates by email and normalized name/phone.
- 3A logic step ranks each candidate's field sources by your trust table and picks the surviving value per field.
- 4The merged record is written back to HubSpot and the losing duplicates are flagged merged.
- 5Every field-level decision (winner, loser, source, rule) is inserted into a Postgres audit table.
- 6A Slack summary posts the merge result and a link to the surviving contact.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.