MARKETING

Attendee vs No-Show Webinar Follow-Up Split

Reads the Zoom attendance report after a webinar and routes attendees into a recap-and-next-step drip while no-shows get a watch-the-replay drip.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom webinar endedZoomZoom
  • ActionFetch participant and registrant listsZoomZoom
  • LogicSplit into attendees vs no-shows
  • ActionDraft both follow-up sequencesOpenAI
  • OutputEnroll contacts in matching HubSpot workflowHubSpotHubSpot

What it does

Not everyone who registered showed up, and they should not get the same email. This workflow reads the Zoom attendance report, splits registrants into attendees and no-shows, and uses OpenAI to draft two different follow-up sequences: a deeper next-step path for people who watched live, and a lighter replay-first path for people who missed it. Each contact is enrolled into the matching HubSpot workflow.

When to use it

Use it whenever attendance lags registration and you want the follow-up tone to reflect whether someone actually attended. It removes the manual export-and-segment step teams usually skip.

How it works

  1. 1Zoom signals the webinar has ended and the attendance report is ready.
  2. 2The flow pulls the participant list and the registrant list from Zoom.
  3. 3A logic step diffs the two lists into attended and no-show buckets.
  4. 4OpenAI drafts two sequences: attendees get a recap plus a clear next action; no-shows get a replay nudge and a soft re-invite.
  5. 5Each contact is enrolled into the correct HubSpot nurture workflow based on its bucket.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  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.