LEAD GENERATION

Conference Attendee Scrape to Deduped Airtable Leads

Scrapes a public conference attendee or speaker page with Apify, normalizes each person, and upserts deduped lead records into Airtable so the same attendee never lands twice.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggermanual
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerManual run with conference URL
  • ActionScrape attendee list with ApifyApify
  • LogicNormalize records and build dedupe key
  • LogicCheck Airtable for existing keyAirtableAirtable
  • ActionUpsert new leads into AirtableAirtableAirtable
  • OutputReport new vs skipped counts

What it does

Pulls the public attendee, speaker, or exhibitor list from a conference website, turns each entry into a clean lead record (name, title, company, profile URL), and writes it into Airtable while skipping anyone already in your base.

When to use it

Run it the week a conference publishes its agenda or attendee directory. Ideal when you repeatedly mine events for pipeline and keep re-importing the same people, creating duplicate rows your SDRs waste time on.

How it works

  1. 1You kick the run off manually and pass the conference page URL.
  2. 2Apify scrapes the rendered page and returns a raw list of attendee blocks.
  3. 3A normalize step trims whitespace, splits full names, and derives a stable dedupe key from email-or-name+company.
  4. 4A dedupe check queries Airtable for the key; existing matches are dropped, new ones pass.
  5. 5New leads are upserted into the Leads table, tagged with the event name and scrape date.
  6. 6A run summary reports counts of new versus skipped records.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ApifyActors, scrapers, datasets.
  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.