PROJECT MANAGEMENT
Triage Loom standup blockers and route them across the org
An agent watches new Loom standups, extracts blockers, decides whether each belongs to engineering, design, or ops, and opens it in the right board (ClickUp or Linear)…
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom standup videoLoom
- ActionTranscribe and extract blockersLoom
- ActionClassify owner and destinationOpenAI
- LogicRoute engineering vs. other
- ActionCreate task in Linear or ClickUpLinear
- OutputPost routing recap to SlackSlack
What it does
This is the smart dispatcher for async standups. An agent transcribes each new Loom video, pulls out blockers, and reasons about where each one actually belongs — a build failure goes to the Linear engineering board, a missing asset goes to the ClickUp design board — then files it with a suggested owner and a one-line rationale.
When to use it
Use it when standup blockers span multiple teams and tools, and a single fixed destination doesn't fit. Ideal for cross-functional squads where routing a blocker correctly is half the battle.
How it works
- 1A new Loom standup video triggers the agent.
- 2The agent fetches the transcript and extracts each distinct blocker.
- 3For every blocker it classifies the owning function and picks the destination system and likely owner.
- 4A logic branch routes engineering blockers to Linear and everything else to the relevant ClickUp board.
- 5The task is created in the chosen system with the rationale and Loom link attached.
- 6A consolidated routing recap is posted to Slack so leads can override any misroute.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect ClickUpDocs + tasks + chats in one workspace.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.