LEAD GENERATION

Compile a Post-Event Reconciliation Digest of Scans, Matches, and Booked Meetings

After the conference ends, this scheduled workflow reads the reconciled Airtable roster, tallies net-new versus existing leads and meetings booked.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run the morning after event end
  • ActionRead reconciled roster and meetings from AirtableAirtableAirtable
  • LogicTally tags, net-new count, and meetings-booked rate
  • OutputEmail leadership the recap with deduped CSV via GmailGmailGmail

What it does

Leadership wants one honest number after a show: how many real, new leads did we get, and how many turned into meetings? This workflow reads the fully reconciled Airtable roster, computes the breakdown — total scans, unique people, net-new, existing contacts, customers, and intro meetings booked — and sends a tidy recap so the team isn't arguing over raw scan counts.

When to use it

Schedule it to run the day after the event closes, once dedupe and meeting-booking flows have finished. Use it to wrap each conference with a defensible ROI summary instead of an inflated badge-scan total.

How it works

  1. 1A scheduled trigger fires the morning after the event end date.
  2. 2The flow reads the reconciled roster and meeting records from Airtable.
  3. 3It tallies scans, unique people, and each lead tag, plus how many intro meetings were booked.
  4. 4It computes a net-new lead count and a meetings-booked rate against unique attendees met.
  5. 5It emails leadership a formatted recap via Gmail with the deduped lead list attached as a CSV.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect GmailRead, draft, send, label.
  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.