PROJECT MANAGEMENT
Retro Blocker Triage to GitHub Issues and PagerDuty
Parses a Zoom retro transcript, separates engineering blockers from general action items, opens GitHub issues for the blockers.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom retro recording completedZoom
- ActionFetch recording transcriptZoom
- ActionClassify blockers vs action items with severityOpenAI
- LogicBranch on blocker severity
- ActionOpen labeled GitHub issues for blockersGitHub
- OutputPage on-call for critical blockersPagerDuty
What it does
This workflow reads a completed Zoom retro, classifies each surfaced item as either a routine action item or an engineering blocker, and routes them differently. Blockers become GitHub issues in the relevant repo with severity labels, and any blocker the team called out as actively breaking work triggers a PagerDuty alert so it does not wait for the next standup.
When to use it
Use it when retros regularly surface real engineering blockers that need tracking in GitHub and, occasionally, immediate escalation. It keeps low-severity follow-ups as ordinary issues while ensuring a critical blocker gets a human paged the same day.
How it works
- 1A Zoom recording-completed event fires for the retro.
- 2The transcript is fetched from Zoom.
- 3OpenAI classifies items into blockers versus action items and tags each blocker with a severity.
- 4A logic step branches on severity.
- 5Every blocker is opened as a labeled GitHub issue.
- 6Critical blockers additionally trigger a PagerDuty incident routed to the on-call engineer.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.