CRM
Approved-Merge Executor with Survivorship Write-Back
Picks up merge pairs a reviewer approved in the Postgres queue, applies field-level survivorship rules.
How it runs
The automated pipeline, trigger to output.
- TriggerPoll Postgres for approved mergesPostgres
- ActionLoad full records from both CRMsSalesforce
- LogicResolve fields via survivorship rules
- ActionWrite merged record to HubSpotHubSpot
- ActionStamp queue row with merge outcomePostgres
- OutputPost Slack merge confirmationSlack
What it does
This is the executor half of the merge pipeline. It reads pairs marked approved in the Postgres queue, resolves each field with survivorship rules (most-recently-updated wins, non-empty beats empty, primary CRM breaks ties), writes the merged values to the surviving record in both Salesforce and HubSpot, and marks the duplicate as merged. Every action is logged back to the queue row for audit.
When to use it
Pair this with a queue-building workflow. Once a human approves a merge, you want it applied consistently and reversibly across both CRMs without manual copy-paste.
How it works
- 1A short-interval schedule polls the Postgres queue for approved, unprocessed rows.
- 2For each pair, load full records from Salesforce and HubSpot.
- 3A logic step computes the survivorship-resolved field set.
- 4Write merged fields to the surviving Salesforce account and HubSpot company.
- 5Mark the losing record as merged and stamp the queue row with the outcome.
- 6Post a Slack confirmation summarizing what changed.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect HubSpotCRM, deals, marketing, support.
- 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
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.