CRM
Duplicate Merge with Slack Approval Gate for Low-Confidence Matches
Catches likely-duplicate HubSpot contacts, auto-merges high-confidence matches by survivorship rules.
How it runs
The automated pipeline, trigger to output.
- TriggerHubSpot contact created or updatedHubSpot
- ActionFind candidates and score match confidenceHubSpot
- LogicBranch by confidence: auto-merge vs human review
- ActionRequest approve/reject decision in SlackSlack
- ActionMerge survivor into HubSpot after decisionHubSpot
- OutputLog final decision and sources to PostgresPostgres
What it does
This workflow splits duplicate handling by confidence. High-confidence matches (exact email plus matching domain) merge automatically using source-trust survivorship. Low-confidence matches (fuzzy name, shared phone, different email) are paused and sent to Slack with the proposed survivorship outcome, where a reviewer approves or rejects before any change is committed.
When to use it
Use it when wrong merges are costly and you want automation for the obvious cases but a human in the loop for the ambiguous ones. Good for teams that tried full auto-merge and got burned by false positives.
How it works
- 1A HubSpot contact create/update event triggers the flow.
- 2The flow finds candidate duplicates and computes a match-confidence score.
- 3A logic branch routes high-confidence matches straight to survivorship merge; low-confidence matches go to the approval path.
- 4For low-confidence matches, Slack posts the proposed merge with approve/reject actions and the flow waits for the response.
- 5Approved or auto merges write the survivor back to HubSpot.
- 6Every decision (auto, approved, rejected, with reviewer and winning sources) is logged to Postgres.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.