MARKETING

Split Webinar Follow-Up by Attendance

After a Zoom webinar ends, pulls the attendance report and sends attendees a thank-you with resources while sending no-shows a separate "watch the replay" email.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom webinar endedZoomZoom
  • ActionFetch attendance report from ZoomZoomZoom
  • LogicLabel each registrant attended or no-show
  • ActionSend attendee thank-you and no-show replay emailsGmailGmail
  • OutputLog final status per person in CodaCodaCoda

What it does

When a Zoom webinar ends, this workflow retrieves the official attendance report and branches the follow-up: people who showed up get a thank-you with slides and next steps, while registrants who missed it get a recovery email pointing to the replay.

When to use it

Use it whenever a one-size-fits-all follow-up wastes the moment. Attendees and no-shows need different messages, and doing it by hand after every event is error-prone and slow.

How it works

1. A Zoom webinar-ended event triggers the run. 2. The flow fetches the attendance report listing who joined and for how long. 3. A logic branch compares the registrant roster against the attendee list to label each person attended or no-show. 4. Gmail sends the thank-you-with-resources email to attendees and the replay-recovery email to no-shows. 5. Each person's final status and email sent are recorded in the Coda tracker for reporting. Your audience gets a relevant message either way, and the marketing team gets clean attended-vs-missed numbers without manual reconciliation.

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 CodaDocs, packs, 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.