AI & RAG
Incident-Time ADR Lookup for On-Call
When a PagerDuty incident triggers, retrieves the ADRs relevant to the affected service, surfaces accepted constraints and any superseded ones to avoid.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggers for a servicePagerDuty
- ActionRetrieve ADRs scoped to the affected serviceConfluence
- LogicSeparate binding constraints from superseded traps
- ActionWrite concise cited incident context noteOpenAI
- OutputPost context note to the incident channelSlack
What it does
Gives on-call responders the architectural context behind a failing service the moment an incident opens. It maps the alerting service to its governing Architecture Decision Records, pulls the accepted constraints (failover strategy, data-residency rules, retry policy) and explicitly flags any superseded decision so nobody reverts to an old pattern under pressure — all cited by ADR number.
When to use it
During incidents where responders don't know the deliberate design choices behind a service and risk "fixing" something that was decided on purpose. Best for on-call teams who want decision context delivered automatically, not dug out at 3am.
How it works
- 1A PagerDuty incident triggers and names the affected service.
- 2ADRs scoped to that service are retrieved from Confluence.
- 3A logic step separates currently-binding constraints from superseded decisions to avoid.
- 4OpenAI writes a concise context note: the live constraints, the traps, and citations.
- 5The note is posted to the incident's Slack channel for responders.
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.