SUMMARIZATION
Daily Honeycomb latency-drift digest to Notion
Every morning, compares yesterday's span latencies to the trailing week, narrates the services that drifted slower, and appends a dated digest entry to a Notion performance log.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule fires
- ActionQuery per-service p95/p99 for day + trailing weekHoneycomb
- LogicCompute drift per service, flag over threshold
- ActionNarrate movers and recoveriesOpenAI
- ActionAppend dated digest entry to Notion logNotion
- OutputPost one-line top-regression summary to SlackSlack
What it does
On a daily schedule, this workflow scans Honeycomb for latency drift across your top services, comparing the prior day's p95/p99 against a trailing-week baseline. It writes a short narrative ranking the services that crept slower (or recovered) and appends a dated entry to a Notion performance log so the team has a searchable history of latency health.
When to use it
Use it for slow-burn regressions that never trip an alert but quietly degrade week over week. A daily digest catches the 8% creep before it becomes a 40% incident, and Notion gives you the paper trail for retros.
How it works
- 1A scheduled trigger fires each morning before standup.
- 2The workflow queries Honeycomb for per-service p95/p99 over the last day and the trailing week.
- 3It computes drift per service and flags those exceeding the drift threshold.
- 4An LLM narrates the movers, calling out the worst regressions and any recoveries in plain English.
- 5The dated digest is appended as a new block to the Notion performance log page.
- 6A one-line summary with the top regression posts to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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 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.