SUMMARIZATION

Sentry Release Regression Log to Notion

On each Sentry release deploy, compares stability against the prior release and appends a structured regression-history entry to a Notion database for trend tracking.

CategorySummarization
Enginesim
Difficultybeginner
Triggerevent
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSentry release deployedSentrySentry
  • ActionFetch new vs prior release metricsSentrySentry
  • ActionSummarize verdict and structured fieldsOpenAI
  • OutputAppend regression entry to Notion DBNotionNotion

What it does

Builds a durable, searchable history of release stability. Every time a new release deploys, it computes the crash-free and error-budget deltas versus the previous release, summarizes the outcome, and writes a structured row to a Notion database so the team can see stability trends across many deploys, not just the latest one.

When to use it

Use it when you want a long-lived record of which releases regressed and why, for retros, postmortems, or quarterly reliability reviews. Complements alerting flows by giving you the historical picture.

How it works

  1. 1A Sentry release-deployed event triggers the flow.
  2. 2Release-health metrics are pulled for the new and prior releases.
  3. 3The deltas are computed and an LLM produces a one-paragraph verdict plus structured fields (crash-free change, budget burn, regression yes/no).
  4. 4A new page is appended to the Notion regression-history database with those fields populated.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.