CRM
Salesforce ↔ HubSpot Dedup with Field-Level Survivorship Rules
Reconciles contacts shared between Salesforce and HubSpot using configurable per-field survivorship rules (e.g.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled reconciliation pass
- ActionPull overlapping contacts from both CRMsSalesforce
- LogicApply per-field survivorship rules
- LogicDiff golden record vs each source
- ActionPush deltas to Salesforce + HubSpotHubSpot
- ActionAudit fired rules to PostgresPostgres
- OutputSlack digest of changesSlack
What it does
Merges the same contact across Salesforce and HubSpot by applying explicit survivorship rules per field rather than blanket last-write-wins. You declare which system is authoritative for each attribute — Salesforce for account/owner, HubSpot for marketing engagement and email — and it assembles a golden record honoring those rules, then syncs it both ways.
When to use it
When Salesforce is your system of record for revenue but HubSpot owns marketing, and you need one trustworthy contact in each without one team's data clobbering the other's.
How it works
- 1A schedule starts the reconciliation pass.
- 2Pull overlapping contacts from Salesforce and HubSpot, joined on email and external IDs.
- 3For each pair, apply the survivorship ruleset field by field to build a golden record.
- 4Diff the golden record against each source to find what must change.
- 5Update Salesforce and HubSpot with their respective deltas.
- 6Write one audit row per applied rule (field, chosen source, value) to Postgres.
- 7Send a Slack digest of records changed and rules triggered.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect HubSpotCRM, deals, marketing, support.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.