LEAD GENERATION

Conference Attendee Scrape with Territory-Based Rep Routing

Scrapes the attendee list, dedupes against the CRM, then routes each net-new prospect to the owning rep by territory and drops them into a per-rep Notion target board.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggermanual
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator starts run with attendee URL
  • ActionScrape attendee listApify
  • ActionDedupe against CRMAttio
  • LogicRoute prospects to reps by territory
  • ActionWrite per-rep target boardsNotionNotion
  • OutputNotify each rep their board is readyMicrosoft Teams

What it does

This scrapes a conference attendee list, removes contacts already in your CRM, and assigns every remaining net-new prospect to the right rep based on territory rules (region or company size). Each rep gets their own pre-event target board they can work independently.

When to use it

Run it for events your whole team attends, when leads need to be split fairly and unambiguously so no two reps chase the same booth and nothing falls through the cracks.

How it works

  1. 1Operator starts the run with the attendee-list URL.
  2. 2Apify scrapes attendee names, titles, companies, and regions.
  3. 3Each contact is matched against the CRM and known ones are dropped.
  4. 4A routing step assigns each net-new prospect to a rep using territory rules.
  5. 5Prospects are written to per-rep boards in Notion, grouped by owner.
  6. 6Each rep is notified in Microsoft Teams that their target board is ready.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ApifyActors, scrapers, datasets.
  2. 2
    Connect AttioReal-time CRM with structured data + powerful views.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  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.