PROJECT MANAGEMENT
Turn Loom standup videos into ClickUp blocker tasks
When a teammate posts a Loom standup video, transcribe it, extract any blockers they mention, and open a ClickUp task for each one so nothing said out loud gets lost.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom standup video postedLoom
- ActionFetch video transcriptLoom
- ActionExtract blockers from transcriptOpenAI
- LogicAny blockers found?
- ActionCreate a ClickUp task per blockerClickUp
- OutputReturn links to created tasksClickUp
What it does
Every async standup recorded in Loom gets read for you. The workflow pulls the transcript, asks an LLM to isolate concrete blockers ("I'm stuck waiting on the API key"), and files each as a ClickUp task tagged to the speaker, so spoken-only impediments become tracked work instead of evaporating.
When to use it
Use it when your team does daily video standups in Loom and blockers regularly get mentioned but never make it onto the board. Ideal for distributed teams across time zones where no one is in a live call to catch and assign follow-ups.
How it works
- 1A new Loom video lands in your standup space and fires the trigger.
- 2The workflow fetches the video transcript from Loom.
- 3An OpenAI call classifies the transcript and extracts a structured list of blockers, each with a short title and the affected work item.
- 4A logic step checks whether any blockers were found; clean standups exit quietly.
- 5For each blocker, a ClickUp task is created in the team's board, assigned to the recorder and tagged `blocker`.
- 6The new task links are posted back as the delivery so the recorder sees exactly what was filed.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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 Project Management workflows
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.
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.
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.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
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.
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…
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.