SUMMARIZATION
Weekly Crash-Free Trend Report to Confluence
Each week, gathers crash-free rates from the three most recent Sentry releases and publishes a narrative trend report — with the regression analysis written in prose.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery crash-free rates for three most recent releasesSentry
- ActionWrite the deploy-over-deploy trend narrativeOpenAI
- LogicTag weekly status: improving, flat, or regressed
- OutputPublish dated section to Confluence release-health pageConfluence
What it does
Once a week this workflow assembles crash-free session and user rates from your three latest Sentry releases and publishes a written trend report to Confluence. The report reads as a short stability narrative comparing the deploys, suitable for engineering managers and stakeholders who do not live in Sentry.
When to use it
Use it for a regular release-health cadence that feeds into ops reviews or QBRs. It is the right fit when leadership wants a readable weekly summary rather than ad-hoc alerts, and when you keep engineering documentation in Confluence.
How it works
- 1A weekly schedule triggers the run.
- 2The flow queries Sentry for crash-free metrics across the three most recent releases.
- 3An LLM step writes a trend narrative describing how stability moved deploy over deploy, calling out any regression and its magnitude.
- 4A logic step tags the week's overall status as improving, flat, or regressed for the page heading.
- 5The report is published as a new dated section on the rolling Confluence release-health page.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.