CRM
Nightly Salesforce duplicate scan with field-conflict report
Each night it scans Salesforce Leads and Contacts for duplicate clusters, builds a field-by-field conflict table for each cluster.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery Salesforce Leads and ContactsSalesforce
- LogicCluster duplicates and diff conflicting fields
- ActionPersist clusters and conflicts to PostgresPostgres
- OutputSend conflict-resolution digest to SlackSlack
What it does
Runs a scheduled sweep over Salesforce to find clusters of duplicate Leads and Contacts, then produces a per-cluster table showing exactly which fields disagree (different phone, title, company) so a RevOps owner can approve merges with full context.
When to use it
Use this when your Salesforce org is too messy for blind auto-merge and you need a human to adjudicate conflicting field values. Ideal for nightly hygiene where you want a digest of what to merge rather than silent changes to records reps depend on.
How it works
- 1A nightly schedule starts the run.
- 2Query Salesforce for Leads and Contacts, blocking candidates by email domain and last name to keep comparisons cheap.
- 3Cluster records that match on email or fuzzy name+company.
- 4For each cluster, diff every field and flag the ones where values conflict, picking a suggested survivor by most-recent activity.
- 5Write the clusters and conflict tables to Postgres for an audit trail.
- 6Send a Slack digest with each proposed merge, the winning record, and the conflicting fields highlighted.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.