ENGINEERING
Nudge for a runbook update when a service PR merges
When a pull request merges to a service's default branch, checks whether that service's Confluence runbook has been touched recently and, if not, opens a GitHub follow-up issue…
How it runs
The automated pipeline, trigger to output.
- TriggerPR merged to default branch (GitHub)GitHub
- ActionRead service runbook last-edited date from ConfluenceConfluence
- LogicBranch on runbook older than freshness window
- ActionOpen GitHub follow-up issue linking the PRGitHub
- OutputDM the PR author in Slack to refresh the runbookSlack
What it does
Catches runbook drift at the moment it happens. The instant a PR merges into a service's main branch, it inspects when that service's runbook was last edited and, if the runbook is older than a freshness threshold, it files a tracked follow-up issue and reminds the merging author to confirm the runbook still holds.
When to use it
Use it on services where code moves fast and runbooks quietly rot. Tying the reminder to the merge event puts the prompt in front of the person with the most context, instead of weeks later in a batch report.
How it works
- 1A GitHub pull-request-merged event triggers the flow.
- 2It looks up the service's runbook in Confluence and reads its last-edited date.
- 3A branch checks whether the runbook is older than the configured freshness window.
- 4If fresh, the flow exits quietly with no noise.
- 5If stale, it opens a GitHub issue titled with the service and links the merged PR.
- 6It posts a Slack direct message to the PR author asking them to review and refresh the runbook.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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
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.