ENGINEERING
Page on-call when a PR breaches review SLA
When a pull request labeled urgent goes past its review SLA without an approval, it triggers a PagerDuty alert to the on-call engineer and notifies the engineering channel.
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent schedule poll
- ActionFilter to urgent-labeled open PRs and measure waitGitHub
- LogicDetect SLA breach with no approval
- ActionTrigger PagerDuty incident to on-callPagerDuty
- OutputPost breach context to engineering channelSlack
What it does
For PRs that genuinely can't wait (hotfixes, incident follow-ups), this workflow enforces a review SLA. Once an urgent-labeled PR exceeds its allowed wait time without an approving review, it pages the on-call engineer through PagerDuty and posts to the engineering channel so the right person responds in minutes, not hours.
When to use it
Use it for repos where some PRs are time-critical and a missed review has real cost (production fixes, customer-blocking changes). It's deliberately scoped to labeled-urgent PRs so it doesn't page anyone for routine work.
How it works
- 1A schedule polls open PRs on a tight interval.
- 2The flow filters to PRs carrying the urgent label and measures time since they were opened or last reviewed.
- 3A branch checks whether an urgent PR has crossed its SLA with no approval yet.
- 4On breach it triggers a PagerDuty incident targeting the current on-call rotation.
- 5It posts the breaching PR and its wait time to the engineering Slack channel so the team has context.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.