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.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom standup uploadedLoom
- ActionRetrieve transcript from LoomLoom
- ActionExtract blockers and resolve ownersHugging 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
- 1A new Loom upload in the tracked workspace triggers the run.
- 2The video's transcript is retrieved from Loom.
- 3A Hugging Face model extracts blocker statements and the named or implied owner for each.
- 4A logic step filters out runs with no blockers so quiet days send nothing.
- 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.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect OutlookMail, calendar, contacts.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
