AI & RAG
Weekly runbook coverage gap reporter
Each week, reviews recently resolved PagerDuty incidents against the postmortem knowledge base and reports which incident types have no remediation precedent.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull resolved incidents from the past week from PagerDutyPagerDuty
- ActionScore retrieval coverage for each incident against Postgres indexPostgres
- LogicCluster incidents that fall below the coverage threshold
- ActionGenerate ranked coverage-gap reportOpenAI
- OutputPublish report to Confluence and announce in SlackConfluence
What it does
Finds the holes in your runbook coverage. It compares the past week's resolved incidents against what the postmortem RAG index can actually answer, and produces a prioritized list of incident patterns that lack documented remediation.
When to use it
Use it to drive a documentation backlog from real operational pain. Best for teams that want their postmortem writing effort aimed at the gaps that keep biting on-call, rather than guessing what to write up.
How it works
- 1A weekly schedule kicks off the review.
- 2The workflow pulls the week's resolved incidents from PagerDuty.
- 3For each incident it runs retrieval against the postmortem index in Postgres and scores whether a confident precedent exists.
- 4Incidents below the coverage threshold are clustered by service and failure signature.
- 5An LLM writes a ranked 'document these next' report with example incidents per gap.
- 6The report is delivered to the team's Confluence space and announced in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI & RAG workflows
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.
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.
Grounded reply suggestions for inbound sales email
Reads inbound prospect emails, retrieves the matching answers from your Coda hub.
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.
On-Call Spec Answerer from Dropbox Engineering Corpus
Answers on-call questions posted in a Slack channel by retrieving the most relevant Dropbox engineering specs and replying with a grounded, source-cited answer in the thread.
Agentic Deep-Dive API Researcher for Hard Spec Questions
An agent fielded via webhook that answers multi-part API questions by iteratively searching OpenAPI specs, changelogs, and Confluence runbooks.
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.