SUMMARIZATION

Loom Weekly Standup Digest to Slack

Rolls up the week's Loom standups into a single threaded Slack post for the team channel, leading with blockers and owners and linking each summary back to its source video.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionFetch trailing-7-day Loom standups + transcriptsLoomLoom
  • ActionSummarize each and tag blockers with ownersHugging FaceHugging Face
  • LogicOrder digest: blockers first, then per-person
  • OutputPost digest to Slack with threaded per-person linksSlack

What it does

Once a week this workflow gathers every standup Loom from the past seven days, transcribes and summarizes them, and posts one digest to your team's Slack channel. Blockers and their owners lead the message; per-person summaries follow in a thread, each with a jump link to the original recording.

When to use it

Use it when standups live in Loom but your team's attention lives in Slack. It brings the weekly signal to where people already are, without forcing anyone to open the videos.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2Loom returns the trailing-7-day standups and their transcripts.
  3. 3A Hugging Face model summarizes each and tags blockers with owners.
  4. 4A logic step orders the digest: blockers first, then per-person highlights.
  5. 5The main digest posts to the Slack channel; individual summaries land in the thread, each linking to its Loom video.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.