LEAD GENERATION

Conference Attendee Scraper to Warm-Account Research Queue

Scrapes a conference attendee or speaker page, enriches each person and company, scores them against your ICP.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggermanual
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator submits event roster URL
  • ActionScrape attendee list into rowsApify
  • ActionEnrich each company with fresh contextExa
  • ActionScore lead against ICP rubricOpenAI
  • LogicDrop leads below score threshold
  • OutputWrite ranked accounts to research queueAirtableAirtable

What it does

Turns a public conference attendee, speaker, or exhibitor page into a ranked queue of warm accounts your sales team can research. It scrapes the roster, enriches each contact and company, scores fit against your ideal customer profile, and files the keepers in Airtable.

When to use it

Run it the week before or after an event where your buyers gather. Instead of hand-copying a 400-person list, you get a deduped, scored shortlist with company context already attached.

How it works

  1. 1You paste the event roster URL and kick off the run.
  2. 2Apify scrapes the page into structured rows of name, title, and company.
  3. 3Exa pulls fresh company context (size, funding, recent news) for each row.
  4. 4An OpenAI step scores each lead 0-100 against your ICP rubric and writes a one-line rationale.
  5. 5A filter drops anyone below the score threshold.
  6. 6Qualified accounts land in an Airtable queue, sorted high-to-low with enrichment fields populated.

Set it up

What you configure once, before turning it on.

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