LEAD GENERATION

Route webinar no-shows and low-intent attendees into re-engagement tracks

After a webinar, compare registrants against actual attendees and poll scores, then route no-shows to a recording follow-up and low-intent attendees to a nurture sequence.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom webinar endsZoomZoom
  • ActionFetch registrants and scored attendeesZoomZoom
  • LogicSplit into no-show vs low-intent cohorts
  • ActionQueue recording follow-up emailGmailGmail
  • OutputLog cohorts and reasons to AirtableAirtableAirtable

What it does

Splits a webinar's registrant population into actionable cohorts that are easy to miss: people who registered but never showed, and people who attended but answered poll questions with low intent. Each cohort gets a different re-engagement track and is logged so nothing falls through the cracks.

When to use it

Use it when you want to recover pipeline beyond the hot hand-raisers, sending no-shows the recording and nudging low-intent attendees into a longer nurture instead of writing them off.

How it works

  1. 1A completed Zoom webinar triggers the flow.
  2. 2The flow fetches both the registrant list and the attendee list with poll scores.
  3. 3A branch separates three groups: no-shows, low-intent attendees, and everyone else (already handled by hot-lead flows).
  4. 4No-shows get a "send recording" follow-up email queued via Gmail; low-intent attendees get tagged for the nurture sequence.
  5. 5Both cohorts are written to Airtable with their cohort label and reason for audit and reporting.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.