LEAD GENERATION

Daily New-Attendee Watch for an Upcoming Conference

Re-scrapes a conference attendee page every day, detects newly added attendees since yesterday, dedupes them against your CRM, and alerts you only about the net-new ones.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionScrape current attendee listApify
  • LogicDiff against yesterday's snapshot for new arrivals
  • ActionDrop attendees already in CRMAttio
  • ActionSave today's list as next baselineAWS S3
  • OutputEmail digest of net-new attendeesGmailGmail

What it does

Attendee lists grow right up to the event. This scheduled flow re-scrapes the registration page daily, diffs it against the previous snapshot to find newly added attendees, removes anyone already in your CRM, and notifies you of just the fresh net-new prospects.

When to use it

Use it in the final weeks before a conference when registrations are climbing fast and you don't want to re-read the whole list every morning. You only hear about people who appeared since the last check and aren't already known.

How it works

  1. 1A daily schedule triggers the run automatically.
  2. 2Apify scrapes the current attendee list.
  3. 3The flow diffs today's list against the stored snapshot to isolate new arrivals.
  4. 4New arrivals are checked against your CRM and known contacts are dropped.
  5. 5The current list is saved to object storage as tomorrow's baseline.
  6. 6The deduped net-new attendees are delivered as a digest email.

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 AWS S3Buckets, objects, signed URLs.
  4. 4
    Connect GmailRead, draft, send, label.
  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.