LEAD GENERATION

Crawl Multiple Event Sites and Rank Speakers in a Notion Leaderboard

Firecrawl scrapes several conference websites at once, OpenAI normalizes every speaker across events, and the workflow publishes a ranked.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggermanual
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator submits conference site URLs
  • ActionFirecrawl crawls each event siteFirecrawl
  • ActionOpenAI extracts and normalizes speakersOpenAI
  • LogicMerge duplicates and score ICP fit
  • OutputPublish ranked leaderboard to NotionNotionNotion

What it does

Builds a single ranked view of speakers across a whole season of events. Firecrawl crawls each conference site, the workflow consolidates speakers who appear at multiple events, scores them, and renders a sortable leaderboard in Notion the team can plan around.

When to use it

Use it for quarterly event planning when you want to compare targets across conferences in one place — and to spot the high-signal speakers who appear at several events worth a concentrated push.

How it works

  1. 1You start the run with a list of conference website URLs.
  2. 2Firecrawl crawls each site and returns the speaker and agenda pages as clean text.
  3. 3OpenAI extracts speaker records and normalizes names and companies across all events.
  4. 4A logic step merges duplicate speakers, counts cross-event appearances, and assigns an ICP score.
  5. 5Speakers are ranked by combined fit and appearance signal.
  6. 6The ranked leaderboard is published to a Notion database with event tags and source links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FirecrawlCrawl, scrape, structured extract.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.