CRM
Bidirectional HubSpot ↔ Attio Contact Reconciliation with Merge Audit
On a schedule, matches contacts across HubSpot and Attio by email, reconciles conflicting field values using last-modified-wins, writes the merged record back to both CRMs.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionFetch changed contacts from HubSpotHubSpot
- ActionFetch changed contacts from AttioAttio
- LogicJoin on email; split matched vs single-system
- LogicResolve field conflicts (last-modified-wins)
- ActionWrite reconciled record to both CRMsAttio
- OutputLog merges to Postgres audit + Slack summaryPostgres
What it does
Keeps your HubSpot and Attio contact records in sync by finding the same person in both systems and reconciling field-level differences. When the same email exists in both CRMs with conflicting values (different title, phone, company), it applies a last-modified-wins rule, pushes the winning value back to both, and records exactly what changed and why in an immutable Postgres audit table.
When to use it
When sales runs in HubSpot and the ops/data team works in Attio, and the two drift apart. Run it nightly so neither system holds stale truth and you keep a defensible trail of every automated merge.
How it works
- 1A nightly schedule fires the run.
- 2Pull the recently-changed contact set from HubSpot and from Attio.
- 3Join the two sets on normalized email; branch records into matched, HubSpot-only, and Attio-only.
- 4For each matched pair, compare fields and pick the most-recently-modified value per field.
- 5Write the reconciled record back to HubSpot and to Attio.
- 6Insert one audit row per field change (old value, new value, source-of-truth, timestamp) into Postgres.
- 7Post a run summary to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect AttioReal-time CRM with structured data + powerful views.
- 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.