SUMMARIZATION
Post-Incident Reliability Recap from Resolved PagerDuty Incident
When a PagerDuty incident resolves, it gathers the incident's Honeycomb traces and error-budget impact and posts a plain-English recap to MS Teams for non-engineering stakeholders.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolved eventPagerDuty
- ActionQuery Honeycomb traces + budget burn for incident windowHoneycomb
- LogicSkip incidents with negligible budget impact
- ActionDraft plain-English incident recapOpenAI
- OutputPost recap to stakeholder MS Teams channelMicrosoft Teams
What it does
Closes the loop after an incident. When a PagerDuty incident is marked resolved, the workflow pulls the long-running traces from the incident window and the error budget the event consumed, then writes a stakeholder-facing recap: what broke, how long, the customer impact, and how much reliability headroom it cost. It is deliberately not an engineering postmortem — it's the version product and leadership read.
When to use it
Use it when every incident triggers a flurry of "so what actually happened?" questions from outside engineering. It delivers the answer automatically the moment the incident closes.
How it works
- 1A PagerDuty incident-resolved event triggers the workflow.
- 2It uses the incident time window to query Honeycomb for the implicated long-running traces and the SLO budget burned during the outage.
- 3A logic step skips low-impact incidents that consumed negligible budget.
- 4An LLM step drafts a plain-English recap with duration, impact, and budget cost.
- 5The recap posts to the stakeholder MS Teams channel, linked to the closed incident.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.