ENGINEERING
Audit runbook freshness for services that paged this week
Weekly, pulls services that triggered PagerDuty incidents in the last seven days, checks each one's Confluence runbook for recent edits.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the audit
- ActionPull last-7-day incidents grouped by service from PagerDutyPagerDuty
- ActionRead each impacted service's runbook date from ConfluenceConfluence
- LogicKeep services with stale runbooks and score by incident count
- OutputPost prioritized risk report to SlackSlack
What it does
Focuses runbook hygiene on the services that actually hurt. It gathers every service that opened a PagerDuty incident in the past week, then cross-references each against its Confluence runbook's last-updated date, producing a prioritized list of services that paged on-call while running on a stale runbook.
When to use it
Run it as a weekly on-call retro input. A runbook that is stale on a quiet service is low risk; a stale runbook on a service that paged three times last week is exactly where to spend a refresh hour. This workflow ranks by real incident pressure.
How it works
- 1A weekly schedule starts the audit.
- 2It queries PagerDuty for incidents in the trailing seven days and groups them by service.
- 3For each impacted service it reads the runbook's last-edited date from Confluence.
- 4A logic step retains only services whose runbook predates the incident window.
- 5It scores each by incident count so the riskiest land on top.
- 6The ranked report is posted to the on-call Slack channel for the retro.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.