AI & RAG
PagerDuty Incident-to-Runbook Procedure Suggester
On a new PagerDuty incident, retrieves the most relevant runbook remediation sections, drafts a grounded step-by-step suggestion with source links.
How it runs
The automated pipeline, trigger to output.
- TriggerNew PagerDuty incident is createdPagerDuty
- ActionBuild query from alert fields and retrieve runbook sections from PostgresPostgres
- LogicBranch on retrieval confidence; skip suggestion if no relevant procedure
- ActionDraft grounded first-response steps with per-step citations via OpenAIOpenAI
- OutputPost the cited suggestion as a note on the PagerDuty incidentPagerDuty
What it does
Meets responders where the alert lands. When PagerDuty opens an incident, it uses the alert title, service, and summary as the query, retrieves matching runbook sections from the vector index, and asks the model to assemble a concise, grounded set of first-response steps with a citation under each step.
When to use it
Use it to cut time-to-first-action during incidents by surfacing the relevant runbook procedure automatically, so the on-call engineer isn't searching the wiki while paged at 3 a.m.
How it works
- 1A PagerDuty incident-triggered event starts the flow.
- 2The alert fields are combined into a retrieval query and embedded with OpenAI.
- 3The top runbook sections are pulled from Postgres pgvector with their Confluence anchors.
- 4A confidence branch decides whether enough relevant material exists to suggest steps.
- 5OpenAI drafts grounded steps citing each source section, and the suggestion is posted as a note on the PagerDuty incident.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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…
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.
Re-Index API Specs on GitLab Merge to Keep the Answer Bot Fresh
Watches GitLab merges to your API repo, detects changed OpenAPI specs and changelog files, re-chunks and re-embeds only what changed.
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.