CRM
Salesforce Duplicate Account Merge Proposals with Slack Field-Level Review
Scans Salesforce for likely-duplicate Accounts, builds a field-by-field merge proposal with a survivor recommendation per field.
How it runs
The automated pipeline, trigger to output.
- TriggerSalesforce duplicate rule flags matched AccountsSalesforce
- ActionFetch full field set for each candidate recordSalesforce
- LogicCompute per-field survivor recommendation and detect conflicts
- LogicBranch on high-risk field conflicts (owner, revenue, contract)
- ActionPost merge proposal with conflicts to Slack review channelSlack
- OutputOn approval, execute Salesforce merge and confirm in threadSalesforce
What it does
When Salesforce flags potential duplicate Accounts, this workflow pulls the matched records, compares them field by field, and proposes which value should survive for each field (most recently modified, most complete, or highest-trust source). It posts the proposal to a Slack review channel with approve/reject controls and only executes the merge after a human signs off.
When to use it
Use it when your Salesforce dedupe rules surface matches faster than your ops team can safely resolve them, and you want a documented, reviewable trail instead of blind auto-merges that lose data.
How it works
- 1Salesforce Duplicate Rule fires and emits the matched Account IDs.
- 2The workflow fetches the full field set for each candidate record.
- 3It computes a per-field survivor recommendation, flagging conflicts where values genuinely differ.
- 4A branch checks whether any high-risk fields (owner, revenue, contract) conflict.
- 5The proposal is posted to Slack with the recommended merge and the conflicts highlighted.
- 6On approval, the workflow calls the Salesforce merge API and confirms back in the thread.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 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.