CRM
AI Agent Triage for Ambiguous Contact Merge Conflicts
A Paperclip agent works through a queue of merge conflicts that rules couldn't resolve, enriches each candidate with web and CRM context.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule drains conflict queuePostgres
- ActionEnrich pair with web + CRM contextExa
- LogicAgent reasons and writes recommendation
- LogicBranch by confidence (auto vs review)
- ActionRoute uncertain cases to Slack with rationaleSlack
- ActionExecute approved merges in HubSpot + AttioHubSpot
- OutputAudit decision and evidence to PostgresPostgres
What it does
Hands the hard dedup cases — the ones deterministic rules punt on — to an agent. For each ambiguous pair it gathers context (company website, CRM activity history, overlapping deals) to judge whether two records are truly the same person, then writes a plain-language recommendation. Confident merges execute automatically; the rest go to a human with the agent's reasoning attached.
When to use it
When your conflict review queue is a recurring time sink and you want an agent to do the investigative legwork so reviewers approve in seconds instead of researching each pair.
How it works
- 1A schedule wakes the agent to drain the conflict queue from Postgres.
- 2For each pair, the agent enriches with a web lookup and pulls activity from HubSpot and Attio.
- 3It reasons over the evidence and writes a merge recommendation with confidence.
- 4Branch: high-confidence merges execute; uncertain ones route to Slack with the rationale.
- 5Execute approved merges in both CRMs.
- 6Record the agent's decision, evidence, and outcome in the Postgres audit log.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect HubSpotCRM, deals, marketing, support.
- 3Connect AttioReal-time CRM with structured data + powerful views.
- 4Connect ExaNeural search across the web.
- 5Connect SlackChannels, DMs, threads, mentions.
- 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.
