AI AGENTS
On-Call Runbook Walker with Approval Gates
When PagerDuty fires a high-severity incident, an agent pulls the matching Notion runbook and walks it step-by-step in a Slack thread.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- LogicFilter to high-severity actionable pages
- ActionFetch matching runbook from NotionNotion
- ActionPost steps to incident Slack threadSlack
- LogicWait for human approval per command step
- ActionRun approved remediation commandShell
- OutputPost audit summary to Slack threadSlack
What it does
Turns a documented remediation playbook into a guided, auditable response session. The agent fetches the right runbook for the alerting service, posts each step into the incident's Slack thread, and gates every state-changing action behind an explicit human approval before it runs the command.
When to use it
Use it when you have written runbooks but on-call engineers still execute them by hand at 3am, skipping steps or fat-fingering commands. Good for teams that want speed without giving an agent unsupervised write access to production.
How it works
- 1A PagerDuty incident triggers the workflow with the service name and severity.
- 2Logic filters out low-severity and non-actionable alerts so only real pages proceed.
- 3The agent looks up the Notion runbook whose title matches the alerting service.
- 4It posts the parsed step list to the incident Slack thread and waits.
- 5For each command step, it requests an approval reaction; on yes it runs the shell command, on no it skips and logs why.
- 6A final Slack summary records every step taken, who approved it, and the outcome.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect ShellRun sandboxed commands inside the workspace.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.