CRM

Attio AI-Judged Duplicate Merge with Diff Summary Approval

Uses an AI agent to compare suspected duplicate Attio person records, write a plain-English merge rationale and field-by-field diff, then request operator approval before merging.

CategoryCRM
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSuspected duplicate flagged in AttioAttio
  • ActionAgent pulls both full records from AttioAttio
  • ActionAgent judges identity and drafts merge diffOpenAI
  • LogicAuto-dismiss clear non-matches; else approve
  • ActionPost rationale and diff to Slack for approvalSlack
  • OutputApply merge and log rationale in AttioAttio

What it does

When two Attio person records look alike, an AI agent compares them, explains in plain English why they are or are not the same person, and proposes which value wins for each conflicting field. An operator approves the proposal before the merge runs.

When to use it

Use this when simple string matching is not enough and you want reasoning over context, like the same person across two companies, name changes, or shared family emails. Best for teams that value an auditable rationale on every merge.

How it works

  1. 1A suspected-duplicate event from Attio (or a manual flag) triggers the run.
  2. 2The agent pulls both full person records from Attio, including notes and associations.
  3. 3The agent judges whether they are the same entity and drafts a field-by-field merge proposal with a written rationale.
  4. 4A logic step routes clear non-matches to auto-dismiss and everything else to approval.
  5. 5The proposal and diff are posted to Slack for an operator to approve or edit.
  6. 6On approval, the agent applies the merge in Attio and records the rationale on the surviving record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AttioReal-time CRM with structured data + powerful views.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.