SALES

Weekly Loom demo engagement rollup posted to Notion and Slack

Each week, pulls Loom view stats for demos sent that week, joins them to the matching HubSpot deals.

CategorySales
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull week's Loom view statsLoomLoom
  • ActionMatch videos to HubSpot deals + ownersHubSpotHubSpot
  • LogicAggregate per-rep engagement metrics
  • ActionPublish scorecard pageNotionNotion
  • OutputPost digest to SlackSlack

What it does

This workflow gives sales leaders a weekly read on whether personalized Loom demos are actually landing. It collects the week's Loom view data, matches each video to its HubSpot deal and owner, and computes per-rep metrics: demos sent, view rate, average watch percentage, and deals that advanced after watching. It writes a clean scorecard page to Notion and drops a digest in the team Slack channel.

When to use it

Use it when you want to coach reps on demo follow-up and prove (or disprove) that Loom outreach moves deals forward, without anyone assembling the report by hand.

How it works

  1. 1A weekly schedule triggers the rollup.
  2. 2Loom is queried for videos shared and viewed in the past seven days.
  3. 3Each video is matched to its HubSpot deal, owner, and stage movement.
  4. 4Per-rep metrics are aggregated: send count, view rate, average watch %, and post-watch stage changes.
  5. 5A formatted scorecard page is created in Notion.
  6. 6A summary digest with the Notion link is posted to the team Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  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.