CRM
Route High-Risk Attio Merges to Slack for Approval Before Overwriting
Detects Attio person merges where survivorship rules disagree on a protected field (owner, ARR, or contract status) and posts an interactive Slack approval before any value is…
How it runs
The automated pipeline, trigger to output.
- TriggerAttio merge-event webhookAttio
- ActionFetch both records and compute survivorshipAttio
- LogicFlag conflict on protected fields
- ActionPost interactive approval to SlackSlack
- ActionPatch survivor after approvalAttio
- OutputLog decision and approver to PostgresPostgres
What it does
Some merges are too consequential to auto-resolve. This workflow scores each merge for risk, auto-applies safe field choices, and escalates conflicts on protected fields to a human in Slack with one-click approve or reject buttons.
When to use it
Use it when duplicate merges can touch revenue-bearing or ownership fields and you want automation for the easy 80% while keeping a human gate on the risky 20%.
How it works
- 1An Attio merge-event webhook delivers the surviving and losing person record IDs.
- 2The workflow pulls both records and runs survivorship rules to compute proposed winning values.
- 3A logic step flags the merge as high-risk if a protected field (record owner, ARR, contract status) differs between the two records.
- 4Low-risk merges patch Attio immediately; high-risk merges post a Slack message showing the two values and an Approve / Reject action.
- 5On approval the surviving Attio record is patched; every decision and the approver are recorded in a Postgres audit table.
Set it up
What you configure once, before turning it on.
- 1Connect AttioReal-time CRM with structured data + powerful views.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.