PROJECT MANAGEMENT
Turn blockers mentioned in Loom standups into tracked Linear issues
Reads each new Loom standup transcript, detects clearly stated blockers, and creates a Linear issue for any blocker that isn't already tracked.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom standup video postedLoom
- ActionPull transcript and extract blocker + speakerOpenAI
- ActionSearch Linear for an existing matching issueLinear
- LogicSkip if tracked, else create new issue
- ActionCreate assigned, labeled Linear blocker issueLinear
- OutputNotify speaker in Slack with issue linkSlack
What it does
When someone posts a Loom standup, this workflow reads the transcript, identifies any blocker they describe, and checks whether a matching Linear issue already exists. If not, it files a new issue assigned to the speaker, labeled as a blocker for triage. Verbal blockers stop evaporating between standups.
When to use it
When blockers get spoken aloud in standup videos but rarely get logged, so they resurface day after day. Use it to guarantee every stated blocker becomes a trackable, owned work item.
How it works
- 1A new Loom video posted to the standup space triggers the run.
- 2The transcript is pulled and an agent extracts any blocker statements plus the speaker.
- 3Linear is searched for an existing open issue matching the blocker.
- 4Logic decides: skip if already tracked, otherwise proceed.
- 5A Linear issue is created, assigned to the speaker, and labeled 'blocker' for triage.
- 6The speaker is notified in Slack with a link to the new issue.
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.