Automate a weekly CRM clean-up list for duplicates and gaps

CRM records drift: duplicates, missing owners, empty fields. A scheduled agent reads the contacts weekly, lists likely duplicates and gaps with the reason for each, and drafts a clean-up its department head reviews and you approve.

What you’ll set up

Connections

Remote MCP server with CRM read access · Required

You connect it as a remote MCP server (Beta). Reads contacts, companies and chosen fields.

Upgrades

Delivery (channel or inbox)

Delivers the approved output to your channel or inbox.

Inputs

Fields every record needs · Required

List, default owner, email

Matching · Required

Choice of exact email or email and similar names, default exact email

Ready by · Required

Time, default 08:00

Brief · Required

Text, prefilled and editable during setup.

Runs

Runs every Monday at 08:00

Done by Business analyst

You approve before anything goes out.

Set up this job

You approve every report · Free to start

How it runs

One agent does the work. Its department head reviews it, then you approve.

  1. 1Business analyst

    Runs every Monday at 08:00 and prepares the report from your connected sources.

  2. 2COO · Review

    The department head reviews the report before it reaches you.

  3. 3You

    You approve before anything goes out.

What you get

Sample, not live dataSample CRM clean-up list (Sample, not live data)

Sample, not live data. Contacts, companies and counts are invented.

CRM clean-up, week of 2 Nov (sample)

3 likely duplicates, 11 records missing an owner.

Record ARecord BWhy they match
J. Rivera, jr@example.testJo Rivera, jr@example.testSame email

Nothing merged. Needs your approval.

Why CRM data drifts

Every form, import and manual entry can create a second copy of the same person. Over months, reports double count, two reps contact the same lead, and fields such as owner or lifecycle stage go empty. Some CRMs help: HubSpot, for example, compares records daily to surface potential duplicates and lets you merge or reject them individually or in bulk. A weekly review of what remains still catches what built-in rules miss.

How the scheduled job works

You add the job and connect read access to your CRM through a remote MCP server (Beta) you set up. Each week a scheduled agent reads contacts and companies changed in the last seven days, and looks for matching emails, near-identical names at the same company, and records missing the fields you list. Because it reads the records that changed in the last seven days, duplicates where neither record changed this week are not caught, so run a full pass by hand now and then. For each likely duplicate it shows both records side by side with the reason they match. It reads and reports. It merges and edits nothing.

Review and approval

The COO agent, as department head, reviews the list before it goes out: do the matches share a real identifier, are any two people with the same name at a large company wrongly paired, are the missing-field counts right. Then you approve, edit or skip it, and nothing is changed in your CRM until you do. Merging cannot always be undone, so keep every merge as your own decision.

Setting rules that work

Tell the agent which fields matter. A contact without an owner is a different problem from one without a phone number. Start with exact email matches, which are safe, and add fuzzy name matches once you trust the list. Keep a note of pairs you rejected so they do not return each week.

Questions

Start with one report

Set up this job

You approve every report · Free to start