AI & RAG
Suggest the matching runbook when PagerDuty pages on-call
On a PagerDuty incident trigger, retrieves the most similar past incidents from your postmortem corpus and replies with a grounded runbook suggestion — likely cause.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- ActionEmbed alert and vector-search postmortem corpusPostgres
- LogicGate on retrieval confidence
- ActionCompose grounded runbook suggestion with citationsOpenAI
- OutputAdd suggestion as a note on the PagerDuty incidentPagerDuty
What it does
When PagerDuty escalates an incident, this workflow turns the alert summary into a retrieval query, finds the closest historical incidents in your postmortem corpus, and writes a grounded suggestion back onto the PagerDuty incident itself: the most likely cause, the remediation that resolved the prior occurrence, and links to the source postmortems. The responder sees it the moment they acknowledge.
When to use it
When your team relies on PagerDuty for paging and you want the relevant runbook surfaced at the point of acknowledgment instead of buried in a wiki. Best for teams with a meaningful history of recurring incident classes.
How it works
- 1A PagerDuty incident triggers the flow with its title, service, and description.
- 2The alert text is embedded and vector-searched against the postmortem corpus in Postgres.
- 3A confidence gate decides whether matches are strong enough to surface.
- 4An LLM composes a runbook suggestion grounded only on retrieved postmortems, citing each.
- 5The suggestion is added as a note on the PagerDuty incident for the responder.
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.
- 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 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.