PROJECT MANAGEMENT
Link a Loom shared in a GitHub issue comment and append criteria from its transcript
When a GitHub issue comment contains a Loom URL, fetches the video transcript, posts a tidy embed plus an extracted acceptance-criteria checklist back as a follow-up comment.
How it runs
The automated pipeline, trigger to output.
- TriggerNew GitHub issue commentGitHub
- LogicDetect Loom URL in comment body
- ActionFetch Loom transcript by URLLoom
- ActionExtract acceptance criteriaOpenAI
- OutputPost enriched follow-up comment on issueGitHub
What it does
Enriches GitHub issues whenever someone drops a Loom link in a comment. The workflow detects the Loom URL, retrieves the recording's transcript, and replies on the same issue with a clean preview of the walkthrough alongside a checklist of acceptance criteria distilled from the narration.
When to use it
Use it when your engineers work in GitHub Issues and designers share Looms inline in comments. Instead of teammates scrubbing the whole video, the criteria show up in text and stay searchable in the issue thread.
How it works
- 1A new GitHub issue comment triggers the flow.
- 2A logic step scans the comment body for a Loom URL and stops if none is found.
- 3The Loom recording's metadata and transcript are fetched by URL.
- 4An LLM step converts the transcript into a concise acceptance-criteria checklist.
- 5A follow-up comment is posted to the GitHub issue with the Loom preview and the checklist.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LoomVideo transcripts, libraries.
- 3Connect OpenAIModels, embeddings, files.
- 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
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.
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.
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.
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.
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.