LEAD GENERATION

Merge attendee lists across multiple events into one master record

On a schedule, pulls badge-scan exports from several event folders, merges them into a single deduplicated master attendee record.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionGather new exports across event foldersGoogle DriveGoogle Drive
  • ActionNormalize and match against master by email
  • LogicBranch: update existing vs create new record
  • ActionRecompute touch counts and event lists
  • OutputWrite updated master table to AirtableAirtableAirtable

What it does

Consolidates badge data from every event you run into one master attendee table. It dedupes a person across shows — someone scanned at three conferences becomes one record with an attended-events list and a touch count. Repeat attendees, the warmest prospects, rise to the top because the system tracks frequency rather than treating each event as a fresh import.

When to use it

Use it if you work a circuit of events and want a cumulative view of who keeps showing up, instead of siloed per-event spreadsheets. Run it weekly so each new event's export folds into the master automatically.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2The flow gathers all new badge-scan exports across the configured event folders in Google Drive.
  3. 3Records are normalized and matched against the existing master table by email.
  4. 4A branch decides per record: append the event to an existing person, or create a new master record.
  5. 5Touch counts and attended-event lists are recalculated for matched people.
  6. 6The updated master table is written to Airtable with repeat attendees flagged for priority outreach.

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