CRM

Airtable Duplicate Account Cluster Builder with Review Queue

Runs on a schedule to cluster duplicate company records in Airtable by normalized name and domain, writes one merge-proposal row per cluster with field conflicts spelled out.

CategoryCRM
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled nightly scan
  • ActionRead all active Account rows from AirtableAirtableAirtable
  • LogicNormalize and cluster records by name, domain, phone
  • LogicFilter out singleton clusters
  • ActionWrite merge-proposal record with field conflicts to AirtableAirtableAirtable
  • OutputTag proposal into reviewer queue viewAirtableAirtable

What it does

This workflow periodically scans an Airtable Accounts base, groups records that look like the same company (normalized name, shared domain, matching phone), and produces a single merge-proposal record per cluster. Each proposal lists the conflicting field values side by side and a suggested winner, then lands in a review-queue view for an operator to confirm.

When to use it

Use it when your CRM source of truth lives in Airtable and duplicates accumulate from form fills, imports, and manual entry. It gives reviewers a clean, deduplicated work queue instead of scrolling raw rows.

How it works

  1. 1A schedule trigger fires (e.g. nightly).
  2. 2The workflow reads all active Account rows from Airtable.
  3. 3It normalizes name, domain, and phone, then clusters records that match.
  4. 4A filter drops singletons so only real duplicate clusters proceed.
  5. 5For each cluster it builds a proposal with field-level conflicts and a recommended survivor.
  6. 6It writes the proposal back to Airtable and tags it into the reviewer queue view.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    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.