MARKETING

Weekly No-Show Recovery Digest

Each Monday, aggregates the prior week's webinar attendance and recording-recovery results from HubSpot into a performance digest published to Notion and posted to the marketing…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionPull last week's attendanceZoomZoom
  • ActionQuery recovery metricsHubSpotHubSpot
  • LogicCompute recovery rates
  • ActionPublish digest to NotionNotionNotion
  • OutputPost summary to SlackSlack

What it does

This workflow closes the loop on no-show recovery by reporting on it. Every Monday morning it tallies the past week's webinars, computes attendance and no-show rates, measures how many absentees opened the recording email and watched on demand, and turns those numbers into a clean digest your marketing team can act on.

When to use it

Use it when you run webinars regularly and need a recurring scoreboard of which sessions and which recovery sequences actually convert no-shows, without anyone hand-building a spreadsheet each week.

How it works

  1. 1A scheduled trigger fires every Monday at 8am.
  2. 2Pull the past week's webinar list and per-session attendance from Zoom.
  3. 3Query HubSpot for recovery-email opens, recording clicks, and resulting status changes among no-shows.
  4. 4Roll the data into per-webinar and overall recovery metrics.
  5. 5Write the formatted digest to a Notion page and post a summary with the link to the marketing Slack channel.

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
    Connect NotionPages, databases, comments.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.