CRM
HubSpot Fuzzy-Match Duplicate Merge with Slack Approval
Detects likely-duplicate HubSpot contacts using fuzzy name and email matching, then asks an operator to approve or reject each merge in Slack before anything is combined.
How it runs
The automated pipeline, trigger to output.
- TriggerNew or updated HubSpot contactHubSpot
- ActionSearch HubSpot for existing similar contactsHubSpot
- LogicScore fuzzy match; keep pairs above threshold
- ActionPost candidate pair to Slack with Approve/RejectSlack
- LogicWait for human decision
- ActionMerge approved contacts in HubSpotHubSpot
- OutputConfirm merge in Slack threadSlack
What it does
Scans newly created or updated HubSpot contacts, finds probable duplicates already in your CRM, and routes every candidate pair to a Slack channel where a human approves or rejects the merge. No contact is ever merged automatically.
When to use it
Use this when your sales and marketing forms create overlapping records (typos, work vs. personal email, name variants) and you want dedupe hygiene without risking a bad automated merge that destroys lifecycle data.
How it works
- 1A new or updated HubSpot contact fires the trigger.
- 2The flow searches HubSpot for existing contacts and scores each against the new one on name, email, and company similarity.
- 3A logic step keeps only pairs above the fuzzy-match confidence threshold; below it, the run ends silently.
- 4Each surviving pair is posted to Slack with key fields side by side and Approve / Reject buttons.
- 5On approval, the flow calls HubSpot's merge API to combine the records, keeping the older one as primary.
- 6A confirmation with the surviving record link is posted back to the Slack thread.
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
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.
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.
Dormant Account Anniversary Re-engagement Email
Each day, finds Attio accounts whose last activity was exactly N months ago and sends each owner's contact a personalized re-engagement email from Gmail.
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.
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.