SUMMARIZATION
Weekly Sentry regression report to Notion
Every week it analyzes error-rate deltas across all releases, identifies recurring regression patterns.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList the week's production releasesVercel
- ActionFetch per-release health and regression issuesSentry
- LogicCompute weekly deltas; cluster recurring root causes
- ActionWrite narrative report with focus recommendationsOpenAI
- OutputPublish report page to NotionNotion
What it does
It aggregates a week of Sentry release-health data across every production deploy, surfaces the releases that regressed, clusters recurring root-cause themes (e.g., a module that keeps reappearing), and writes a narrative report. The result is a Notion page leadership can read without opening Sentry, including a recommended focus list for the next sprint.
When to use it
Use it for weekly reliability reviews or sprint planning when you want regression trends turned into prose and priorities rather than a dashboard screenshot.
How it works
- 1A weekly schedule kicks off the run.
- 2The flow lists the week's production releases via Vercel.
- 3Sentry returns per-release health metrics and the issues behind each regression.
- 4A logic step computes weekly deltas and clusters issues by recurring component or error type.
- 5An OpenAI step writes the narrative report with a summary, the worst regressions, and recommended focus areas.
- 6The report is published as a new Notion page in the reliability database.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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
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…
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.
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.
Escalate blockers from Loom standups to Slack
Transcribes each new Loom standup video, uses AI to detect blockers and dependencies.
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.