What this automation does
The session ends, and within a few hours every registrant has heard from you with something relevant to how they participated.
- Wait for data. After the scheduled end time, the workflow polls the webinar platform until the attendance report and recording are both available.
- Segment. Each registrant is labeled attended, left early (for example under half the session) or no-show, with join time, duration, poll answers and questions asked.
- Match to CRM. Registrants are matched to contacts in HubSpot or Salesforce by email, and the webinar attendance is written to their timeline.
- Answer questions. Questions that were not answered live are sent to a model with the slide deck and your product docs. It drafts short answers, and the presenter approves them in Slack.
- Send by segment. Attendees get a thank-you with the recording, slides and their question answered. Early leavers get a link that jumps to the part they missed. No-shows get the recording with a three-line summary of what was covered.
- Alert sales. Attendees whose engagement passes the scoring rules become CRM tasks for their owner, with a short note on what they asked and how long they stayed.
When it is worth building
This is worth it if you run webinars at least monthly and follow-up currently happens days later, or as one generic blast to everyone. The most valuable signal from a webinar, who asked what, usually dies in an exported CSV that nobody opens.
If you run two webinars a year, use your webinar platform’s built-in follow-up emails and a manual CSV import. If you run on an all-in-one webinar platform that already syncs attendance into your CRM, start there and build only the parts it lacks, often the question answering and the sales alerts.
Architecture
| Layer | What we use | Why |
|---|---|---|
| Webinar data | Zoom API (webinar registrants, attendance, Q&A and polls) | Source of truth for who came and what they asked |
| Orchestration | n8n with a wait-and-poll loop | Built-in HubSpot, Salesforce, Gmail and Slack nodes; webinar report endpoints called through HTTP Request |
| Identity match | CRM search by email, with a fallback on name and company | People often join with a different email than they registered with |
| Question answers | Claude Sonnet 5.5 with the deck and docs as context | Grounded answers instead of generic ones |
| Approval | Slack interactive message to the presenter | Fast sign-off on anything said about the product |
| Sending | Your marketing email platform or Gmail for one-to-one notes | Segment emails go through your platform; personal answers can come from the presenter |
| Sales handoff | HubSpot or Salesforce tasks | Reps work from their CRM queue, not from a spreadsheet |
How to build it
- Confirm API scope. Check that your webinar plan and app permissions expose registrants, participants, Q&A and polls. Missing scopes are the most common blocker.
- Design the segments and scoring. Write down the duration threshold for early leavers and the scoring rules for sales alerts. Keep scoring rules simple enough that sales can explain them.
- Build the wait-and-poll step. Poll on an interval until reports and the recording are ready, with a maximum wait and an alert if data never arrives.
- Match registrants to CRM. Match by email first, then by name and company domain. Unmatched attendees go to a sheet for review instead of creating duplicate contacts.
- Draft question answers. Feed the question, the asker’s company, the deck text and approved product docs. Instruct the model to say when it does not know and to defer pricing to sales.
- Build segment emails. Use your email platform’s templates with merge fields for the recording link, the timestamp for early leavers and the approved answer.
- Add sales alerts. Create a task for the contact owner with the attendee’s questions, poll answers and minutes attended.
The downloadable starter template below covers the Zoom polling loop, segmentation, HubSpot matching and segment emails.
What breaks in production
- Different join emails. Someone registers with a work email and joins from a personal account. Duration then shows zero for the registrant. Fuzzy matching and the unmatched sheet catch most cases.
- Recording not ready. Sending the no-show email before the recording processes means a broken link. The workflow must check the recording URL works before sending.
- Panelists in the attendee list. Hosts and panelists appear in reports and get thank-you emails. Exclude them by role or email domain.
- Duplicate registrations. People register twice and get two emails. Deduplicate by email before sending.
- Anonymous questions. Some platforms allow anonymous Q&A. Answer these in the general recap, never by guessing who asked.
Timeline and cost
A Zoom and HubSpot or Salesforce setup with segmentation, question answering and sales alerts usually takes one to two weeks. Lumeor builds this in the range of $3,500 to $9,000, depending on the webinar platform, the CRM, how many email variants you want, and whether recordings are trimmed or chaptered automatically. If you want the recording turned into social posts and clips as well, add the content repurposing pipeline. For multi-touch nurture after the first email, see sales follow-up sequences, and the starter template gives you the core flow.
How to measure success
- Hours from webinar end to follow-up sent
- Recording views by no-shows and early leavers
- Reply rate to attendee emails that answered their question
- Meetings booked within 14 days of the webinar, from scored attendees
- Share of attendees matched to a CRM contact automatically