SUMMARIZATION

Crash-Free Release-Health Appendix from Last Three Sentry Deploys

On each new Vercel production deploy, pulls crash-free session and user rates for the last three Sentry releases and writes a plain-English regression narrative as an appendix…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel production deploy succeedsVercelVercel
  • ActionFetch crash-free rates for last three Sentry releasesSentrySentry
  • ActionSummarize the three-deploy trend into a regression narrativeOpenAI
  • LogicFlag whether crash-free delta crosses regression threshold
  • OutputAppend Stability Appendix block to matching Notion release pageNotionNotion

What it does

Every time a new production build lands on Vercel, this workflow compares the freshest Sentry release against the two before it and appends a written health appendix to that release's Notion notes. Instead of a raw metrics table, your team reads a sentence or two: whether crash-free sessions held, slipped, or recovered, and by how much.

When to use it

Use it when you ship to production often and want every release-notes page to carry an honest, automatic stability footnote without an engineer hand-writing it. Ideal for teams who keep customer-facing or internal changelogs in Notion.

How it works

  1. 1A Vercel deployment-succeeded webhook fires with the new release version.
  2. 2The flow queries Sentry for crash-free session and user rates across the last three releases (current plus two prior).
  3. 3An LLM step turns the three-point trend into a short regression narrative, naming the delta and direction.
  4. 4A logic step flags whether the change crosses your regression threshold.
  5. 5The narrative is appended as an "Stability Appendix" block to the Notion page whose title matches the release version.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect SentryErrors, performance, releases.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect NotionPages, databases, comments.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.