SUMMARIZATION
Honeycomb Error-Spike Digest with PagerDuty Escalation
Polls Honeycomb on a short interval for trace error-rate spikes, summarizes the affected traces with OpenAI, posts a digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled poll every few minutes
- ActionFetch error-rate-by-operation vs rolling baselineHoneycomb
- ActionSummarize failing operations and blast radiusOpenAI
- LogicBranch on critical vs moderate severity
- OutputPost digest to Slack and page PagerDuty if criticalPagerDuty
What it does
Watches Honeycomb for sudden increases in span error rate across services. When errors climb, OpenAI summarizes which operations are failing and the probable blast radius, then routes the result by severity: a Slack digest for moderate spikes, a PagerDuty incident for critical ones.
When to use it
Use it when raw alerting is too noisy but you still need fast escalation for genuine incidents. The summary turns a wall of failing spans into one readable paragraph, and the severity branch keeps pages reserved for what actually warrants waking someone.
How it works
- 1A scheduled poll runs every few minutes.
- 2Honeycomb returns current error-rate-by-operation versus the rolling baseline.
- 3OpenAI summarizes the spike: failing operations, error count, and likely user impact.
- 4A logic branch checks severity against the critical threshold.
- 5Moderate spikes post a digest to Slack; critical spikes also open a PagerDuty incident with the summary attached.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
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.
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.
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.