CRM
Salesforce Agentic Duplicate Resolver with Reasoned Survivorship Notes
An agent reviews flagged Salesforce duplicate leads, reasons through field-level survivorship with human-readable justification for each choice, drafts a merge plan.
How it runs
The automated pipeline, trigger to output.
- TriggerSalesforce duplicate set detectedSalesforce
- ActionPull full field set for all records in the duplicate groupSalesforce
- ActionAgent reasons survivorship per field with justification
- LogicRoute low-confidence decisions for mandatory human edit
- ActionFile merge plan with rationale to Notion review docNotion
- OutputExecute Salesforce merge and stamp decision summarySalesforce
What it does
When Salesforce surfaces a duplicate set, an agent examines the conflicting fields and decides which value should survive, writing a short rationale for each pick (for example, why one company name or owner is more trustworthy). It assembles these into a structured merge plan rather than acting blindly.
When to use it
Use it for high-value or ambiguous duplicates where simple recency rules are not enough and a data steward wants reasoning they can audit. Good for enterprise Salesforce orgs with strict data governance.
How it works
- 1A Salesforce duplicate-set event triggers the flow.
- 2The flow pulls the full field set for every record in the duplicate group.
- 3The agent evaluates each conflicting field, chooses a surviving value, and writes a plain-language justification.
- 4A logic step routes low-confidence decisions for mandatory human edits and high-confidence ones for quick approval.
- 5The merge plan with rationale is filed to a Notion review doc.
- 6After the steward approves, the flow executes the Salesforce merge and stamps the record with the decision summary.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect NotionPages, databases, comments.
- 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.