SUMMARIZATION
Weekly Sentry Release-Health Digest to Teams
Once a week rolls up every deploy's Sentry error-rate change versus its predecessor into a single trend narrative and posts a release-health digest to Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList releases deployed this weekSentry
- ActionCompute per-release deltas vs predecessorSentry
- ActionAggregate into weekly trend digestOpenAI
- OutputPost release-health digest to TeamsMicrosoft Teams
What it does
Gives leadership a weekly read on whether shipping is getting safer or riskier. It gathers all releases deployed during the week, computes each one's Sentry error-rate and crash-free delta against the release before it, and synthesizes the set into a single trend narrative — total regressions, biggest offender, net direction of stability — then posts it to a Microsoft Teams channel.
When to use it
Use it for a recurring engineering-health checkpoint where individual per-deploy alerts are too noisy but a once-weekly aggregate trend is exactly the right altitude for managers and stakeholders.
How it works
- 1A weekly schedule triggers the run.
- 2List all releases deployed during the past week.
- 3For each release, fetch Sentry metrics and compute the delta against its predecessor.
- 4Aggregate the deltas into a trend story: counts of regressed versus improved deploys and the standout regression.
- 5Summarize into a concise digest with the week's net stability direction.
- 6Post the digest to Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect OpenAIModels, embeddings, files.
- 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.