CRM
HubSpot Duplicate Merge Guardian with Field-Survivorship Review Queue
Detects likely-duplicate HubSpot contacts, builds a field-by-field survivorship proposal (which value wins per field).
How it runs
The automated pipeline, trigger to output.
- TriggerHubSpot contact created or updatedHubSpot
- ActionSearch HubSpot for duplicate candidates by email, phone, nameHubSpot
- LogicBranch: exit if no strong match, else build survivorship proposal
- ActionPost per-field merge proposal to Slack review queueSlack
- ActionOn approval, call HubSpot merge APIHubSpot
- OutputLog surviving record and merge decision
What it does
It watches HubSpot for newly created or updated contacts, finds probable duplicates, and turns the messy merge decision into a clean approval. Instead of auto-merging and silently destroying data, it produces a per-field survivorship proposal and routes it to a human queue.
When to use it
Use it when your team imports lists or captures leads from multiple sources and you want clean records without risking data loss from a blind auto-merge. Ideal for RevOps teams that need an audit trail for every merge decision.
How it works
- 1A new or updated HubSpot contact fires the trigger.
- 2The flow searches HubSpot for matches on normalized email, phone, and name to find duplicate candidates.
- 3A logic step branches: if no strong match, it exits quietly; if matches exist, it continues.
- 4For each conflicting field (name, title, owner, lifecycle stage), it picks a winner using recency and completeness rules and assembles a survivorship proposal.
- 5The proposal posts to a Slack channel with Approve/Reject actions and a clear before/after diff.
- 6On approval the flow calls the HubSpot merge API and logs the surviving record.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.