PROJECT MANAGEMENT
Reconcile Loom standup videos against Linear board movement to surface silent blockers
Each morning, collects the team's Loom async-standup videos, reads their transcripts, and cross-checks who said they were blocked against which Linear issues actually moved.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule fires after standup window
- ActionFetch last 24h Loom standup videos + transcriptsLoom
- ActionExtract per-person status and blocker mentionsOpenAI
- ActionPull each engineer's Linear issue state changesLinear
- LogicCompare spoken status vs board movement; tag silent blockers
- OutputPost reconciled blocker digest to SlackSlack
What it does
Gathers the daily Loom standup videos from your team's workspace, pulls each transcript, and reconciles spoken updates against real Linear activity. It flags people who said "blocked" but whose issues never moved, and issues that sat untouched despite a verbal commitment. The result is a single Slack digest naming who is genuinely stuck.
When to use it
For distributed teams running async video standups where talk and board state drift apart. Use it when blockers get mentioned on Loom but never make it into the tracker, so they quietly stall.
How it works
- 1A morning schedule fires after the standup window closes.
- 2Loom returns the videos posted to the standup space in the last 24 hours, with transcripts.
- 3An agent extracts each person's claimed status and any blocker language from the transcript.
- 4Linear is queried for each engineer's issue state changes over the same window.
- 5Logic compares spoken status to board movement and tags mismatches as silent blockers.
- 6A formatted blocker digest is posted to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
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.