AI & RAG
Incident Runbook Responder from Postmortem History
When a PagerDuty incident triggers, retrieves the most relevant past postmortems and runbooks and posts a grounded, cited mitigation brief into the incident's Slack channel.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident openedPagerDuty
- ActionRetrieve matching postmortems and runbooksConfluence
- ActionSynthesize grounded mitigation brief with citationsOpenAI
- LogicBranch on retrieval confidence threshold
- OutputPost brief to incident Slack channelSlack
What it does
The moment a PagerDuty incident is opened, this workflow searches your library of past postmortems and runbooks, then drops a concise, citation-backed mitigation brief into the incident's Slack war room — so the on-call engineer starts with what worked last time instead of a blank page.
When to use it
Use it when your team keeps postmortems in Confluence but nobody reads them during a live incident. Ideal for teams with recurring failure modes (cache stampedes, connection pool exhaustion, bad deploys) where the fix is already documented somewhere.
How it works
- 1A new PagerDuty incident fires the trigger, carrying the alert title, service, and severity.
- 2The incident text is embedded and matched against a Confluence space of postmortems and runbooks.
- 3An OpenAI step synthesizes a brief: likely cause, prior occurrences, and the first three remediation steps — strictly grounded in the retrieved docs, with links cited.
- 4A logic gate checks whether retrieval confidence cleared a threshold.
- 5The brief posts to the incident Slack channel; low-confidence cases post a 'no strong match, escalate' note instead.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 & RAG workflows
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
RFP and security questionnaire drafter grounded in Coda
Drafts answers to inbound RFP and security questionnaire questions by retrieving approved language from your Coda hub, then files the cited draft for review before a rep sends 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.