AI & RAG
On-Call Shift Handoff Digest
At shift change, summarizes the last shift's PagerDuty incidents and links each to relevant postmortems, delivering a grounded handoff brief to the incoming on-call engineer.
How it runs
The automated pipeline, trigger to output.
- TriggerShift-change schedule fires
- ActionFetch resolved incidents for the shiftPagerDuty
- LogicSkip digest on a clean shift
- ActionRetrieve related postmortems per incidentPostgres
- ActionWrite grounded handoff summariesOpenAI
- OutputSend digest to incoming on-call in SlackSlack
What it does
At the end of each on-call rotation it assembles a handoff digest: every incident the outgoing engineer handled, what likely caused each, and the postmortems or runbooks most relevant to recurrence — so the incoming engineer inherits context, not just a pager.
When to use it
Use it for teams with rotating on-call where handoffs are verbal, rushed, or skipped. Especially valuable when overnight incidents risk repeating on the next shift without the new responder knowing.
How it works
- 1A scheduled trigger fires at shift boundary.
- 2PagerDuty is queried for incidents resolved during the outgoing shift.
- 3A logic step short-circuits to a quiet 'no incidents' note when the shift was clean.
- 4For each incident, relevant postmortems and runbooks are retrieved from the Confluence-backed Postgres corpus.
- 5OpenAI writes a per-incident handoff summary with cause, status, and recommended watch items, grounded in retrieved sources.
- 6The digest is delivered to the incoming on-call engineer 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 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
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.