CRM
Approved-Merge Executor: Collapse HubSpot Records into the Salesforce Survivor
When a reviewer marks a queued duplicate pair as approved in Coda, this workflow merges the agreed fields into the Salesforce survivor record, archives the HubSpot loser.
How it runs
The automated pipeline, trigger to output.
- TriggerCoda row marked Approved (webhook)HTTP webhook
- LogicValidate both records exist and resolution map is complete
- ActionApply winning field values to Salesforce survivorSalesforce
- ActionArchive HubSpot duplicate with merged-into referenceHubSpot
- OutputPost field-diff audit trail to SlackSlack
What it does
This is the execution half of a human-in-the-loop dedupe process. Once a reviewer approves a merge in the Coda queue, it copies the chosen field values into the designated survivor company in Salesforce, marks the duplicate in HubSpot as merged-and-archived, and records exactly what changed.
When to use it
Pair this with a detection workflow that fills the review queue. Use it when you have decided Salesforce is your system of record post-acquisition and want approved merges applied consistently, with a clean audit log instead of manual copy-paste.
How it works
- 1A webhook fires when a Coda row's status flips to Approved, carrying the survivor ID, loser ID, and the field-resolution map.
- 2A logic step validates that both records still exist and the resolution map is complete.
- 3The flow updates the Salesforce survivor company with the approved winning field values.
- 4It updates the HubSpot duplicate to set a merged-into reference and archive flag so it stops appearing in active views.
- 5A Slack message posts the before-and-after field diff to the audit channel for traceability.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect HubSpotCRM, deals, marketing, support.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect HTTP webhookTrigger any URL on agent actions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Spin up a Monday handoff board for a departing rep's deals
When a rep is deactivated in Salesforce, this creates a Monday.com board with one item per open opportunity so the manager can manually triage and assign each handoff.
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.
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.
Reassign a departed rep's open pipeline by territory
When a Salesforce user is deactivated, this finds all of their open opportunities and reassigns each one to the active rep who owns its territory, then logs the moves.
Escalate opportunities still owned by an inactive rep after grace period
Checks daily for open opportunities that have stayed with an inactive owner past a grace window and escalates each to the regional director by email and Slack with deal context.
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.
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.