LEAD GENERATION

Multi-Scanner Export Cross-Dedupe & Merge

Combines badge-scan exports from multiple booths or devices in Drive, merges duplicate attendees into a single golden record per person.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAll scan exports present in Drive folderGoogle DriveGoogle Drive
  • ActionParse and pool all CSV rows
  • LogicCluster duplicates and merge to golden record
  • ActionWrite deduped master list to AirtableAirtableAirtable
  • OutputPost merge report to SlackSlack

What it does

Reconciles overlapping scan exports from several scanners or booth stations into one clean master list. The same attendee scanned at three booths becomes a single Airtable record that keeps every booth touchpoint and the richest contact fields, so your follow-up team works from truth, not chaos.

When to use it

Run it at the end of a multi-day or multi-booth event when you have several CSVs that overlap. Ideal for large exhibits where attendees get scanned repeatedly and a naive import would triple-count the same person.

How it works

  1. 1The trigger fires when all expected scan exports are present in the Drive folder.
  2. 2Every CSV is parsed and rows pooled into one in-memory dataset.
  3. 3A dedupe logic step clusters rows by email, then fuzzy name plus company.
  4. 4Each cluster is merged into a golden record retaining all booth visit tags.
  5. 5The deduped master list is written to the Airtable leads table.
  6. 6A run report posts merge counts and conflict flags to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect AirtableBases, tables, views, automations.
  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.