PROJECT MANAGEMENT
Page the on-call lead when a late GitHub epic blocks shipping issues
When a GitHub milestone epic passes its due date with open work, finds the issues that depend on it via tracked-by links and pages the on-call engineering lead through PagerDuty…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled milestone check on repo
- ActionFind overdue milestones with open issuesGitHub
- ActionTraverse tracked-by links to collect blocked downstream issuesGitHub
- LogicCompute severity from blocked shipping issues and release proximity
- OutputOpen a PagerDuty incident to the on-call leadPagerDuty
What it does
Treats an overdue GitHub milestone as a milestone-at-risk signal. When such a milestone still has open issues past its date, the flow resolves which downstream issues are blocked through GitHub's tracked-by relationships and escalates to the engineering on-call so a slip cannot silently sink a release.
When to use it
Use it on release-critical repos where an epic dragging late should trigger an active human decision, not a passive notification. Best when you already run PagerDuty for engineering escalation.
How it works
- 1A scheduled check runs against the target repository's milestones.
- 2The flow flags any milestone past its due date that still has open issues.
- 3For each flagged milestone it traverses tracked-by and blocked-by links to assemble the set of downstream issues that cannot proceed.
- 4A branch decides severity from how many shipping-labeled issues are blocked and how close the release tag is.
- 5PagerDuty receives an incident with the at-risk epic, the blocked-issue list, and the computed severity routed to the engineering lead.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.