SUMMARIZATION

Loom Blocker Detector with Owner Email Escalation

Watches for new Loom standup uploads, extracts only the blockers and the people who can unblock them, and emails each owner a targeted action request via Outlook.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Loom standup uploadedLoomLoom
  • ActionRetrieve transcript from LoomLoomLoom
  • ActionExtract blockers and resolve ownersHugging FaceHugging Face
  • LogicSkip if no blockers detected
  • OutputEmail each owner a targeted unblock requestOutlook

What it does

This workflow fires the moment a new standup Loom is posted. It transcribes the video, extracts only the blockers (ignoring routine status), identifies who is responsible for clearing each one, and sends each owner a concise Outlook email naming the blocker, who raised it, and a link to the relevant timestamp.

When to use it

Use it when blockers in async standups go unnoticed for days because nobody watches every video. This routes each blocker straight to the person who can resolve it, the same day it's raised.

How it works

  1. 1A new Loom upload in the tracked workspace triggers the run.
  2. 2The video's transcript is retrieved from Loom.
  3. 3A Hugging Face model extracts blocker statements and the named or implied owner for each.
  4. 4A logic step filters out runs with no blockers so quiet days send nothing.
  5. 5For each blocker, an Outlook email goes to the owner with the blocker text, who raised it, and a deep link to the moment in the 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 OutlookMail, calendar, contacts.
  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.