AI & RAG
PagerDuty Incident Spec-Context Briefing
When a PagerDuty incident triggers, retrieves the relevant Dropbox specs and runbooks for the affected service and posts a grounded incident briefing into the incident's Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- ActionVector-search spec index by service and alert summaryPostgres
- ActionRetrieve matching spec and runbook passagesDropbox
- ActionSynthesize grounded incident briefingOpenAI
- OutputPost briefing with sources to incident Slack channelSlack
What it does
Gives responders instant context the moment an incident opens. It reads the firing PagerDuty alert, pulls the matching engineering specs and runbooks from the Dropbox corpus, and posts a grounded briefing covering what the service does, known failure modes, and documented rollback steps into the incident Slack channel.
When to use it
Use it to cut mean-time-to-context during incidents. Instead of a responder scrambling to find the right design doc, the relevant spec excerpts arrive automatically, scoped to the alerting service.
How it works
- 1A PagerDuty incident trigger fires with the alert payload.
- 2The service name and alert summary are used to vector-search the spec index in Postgres.
- 3Matching spec and runbook passages are retrieved from Dropbox with their paths.
- 4OpenAI synthesizes a tight incident briefing strictly from those passages.
- 5The briefing, with linked sources, is posted to the incident's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DropboxFiles and folders.
- 4Connect OpenAIModels, embeddings, files.
- 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.