CRM

Land Zoom Webinar Engagement Signals in BigQuery for Attribution

On a schedule, exports completed Zoom webinar participation data into a BigQuery table so analysts can model watch-time signals against pipeline and revenue.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList webinars ended in last 24hZoomZoom
  • ActionFetch participant reportsZoomZoom
  • LogicFlatten and de-duplicate to row schema
  • ActionStream rows into BigQueryGoogle BigQueryBigQuery
  • OutputReport rows inserted and skips

What it does

This workflow builds the analytics backbone for webinar attribution. On a daily cadence it pulls participation reports for recently completed Zoom webinars, normalizes per-attendee watch-time and interaction fields, and appends them to a BigQuery table keyed by email and webinar.

When to use it

Use it when marketing ops needs durable, queryable engagement history, joining watch time to opportunities and closed-won, rather than relying on the rolling 30-day window Zoom keeps.

How it works

  1. 1A daily schedule trigger starts the run.
  2. 2An action lists Zoom webinars that ended in the last 24 hours.
  3. 3An action fetches each webinar's participant report with join/leave, minutes, polls, and Q&A.
  4. 4A logic step flattens and de-duplicates rows into a clean per-attendee schema.
  5. 5An action streams the rows into the BigQuery engagement table.
  6. 6An output reports rows inserted and any webinars skipped for missing data.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  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.