MARKETING

Webinar Attendance Sync to HubSpot Workflows

Writes Zoom attendance status back to each HubSpot contact and enrolls no-shows in a recording-recovery list, so your marketers' existing HubSpot workflows take over the nurture.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom webinar endsZoomZoom
  • ActionFetch registrants and participantsZoomZoom
  • LogicBranch by attended vs no-show
  • ActionUpdate contact attendance propertyHubSpotHubSpot
  • OutputAdd no-shows to recovery listHubSpotHubSpot

What it does

This workflow is the bridge between Zoom's webinar data and your HubSpot nurture engine. It reads who attended versus who didn't, then updates a custom contact property on each registrant in HubSpot and adds the absentees to a static recovery list. The actual emails live in HubSpot workflows your team already owns, so messaging stays on-brand and editable without touching automation code.

When to use it

Choose this when HubSpot is your system of record and you want webinar attendance to drive native HubSpot workflows, scoring, and reporting rather than firing emails from a separate tool.

How it works

  1. 1The Zoom webinar.ended event triggers with the session details.
  2. 2Pull the registrant and participant lists from Zoom.
  3. 3For every registrant, branch on whether their email attended or not.
  4. 4Update the HubSpot contact's last_webinar_status property (attended / no_show) and the webinar name.
  5. 5Add each no-show to the designated HubSpot static list, which is the enrollment trigger for your recording-recovery workflow.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.