LEAD GENERATION

ICP-Scored Conference Leads Routed into HubSpot

Scrapes a conference attendee list, enriches and scores each person against your ICP with Exa context, then routes high-fit leads into HubSpot and low-fit ones to a nurture list.

CategoryLead Generation
EngineSim + Paperclip
Difficultyadvanced
Triggermanual
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerManual run with attendee directory URL
  • ActionScrape attendee directory with ApifyApify
  • ActionEnrich attendees via ExaExa
  • LogicScore against ICP and assign tier
  • LogicBranch high-fit vs low-fit
  • OutputRoute to HubSpot pipeline or nurture listHubSpotHubSpot

What it does

Converts a scraped attendee list into scored, routed pipeline. Each attendee is enriched with company context from Exa, scored against your ideal-customer profile, and pushed to the right destination in HubSpot based on fit.

When to use it

Use it for large events where the attendee list is too big to triage by hand and you want reps to only see leads that match your ICP, with everyone else parked for nurture instead of discarded.

How it works

  1. 1You start the run with the attendee directory URL.
  2. 2Apify scrapes the directory into structured attendee rows.
  3. 3Exa enriches each row with company size, industry, and a recent signal.
  4. 4A scoring step rates each lead against ICP rules and assigns a fit tier.
  5. 5A branch routes high-fit leads as HubSpot contacts in a sales pipeline and low-fit leads into a separate nurture list.
  6. 6The run outputs tier counts so you can gauge the event's quality at a glance.

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 HubSpotCRM, deals, marketing, support.
  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.