SUMMARIZATION

Daily Sentry Release Regression Log in Notion

Each morning compares yesterday's deploys against their predecessors in Sentry and writes a dated regression log entry in Notion summarizing which releases moved error rates…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList releases deployed in last 24hSentrySentry
  • ActionFetch per-release error deltas vs predecessorSentrySentry
  • ActionCompose dated regression narrativeOpenAI
  • OutputAppend entry to Notion regression logNotionNotion

What it does

Builds a running historical record of release health. On a schedule it walks the deploys from the last 24 hours, pairs each with the release it replaced, gathers the Sentry error-rate and crash-free deltas, and composes one dated narrative covering the day's release-health story. It appends that entry as a new page in a Notion database so the team has a searchable regression log.

When to use it

Use it when you want a durable, reviewable trail of how each deploy affected stability — for retros, on-call handoffs, or proving a slow drift over weeks that no single alert would surface.

How it works

  1. 1A daily schedule triggers the run.
  2. 2Pull the list of releases deployed in the trailing 24 hours.
  3. 3For each, fetch Sentry error and session metrics for it and its predecessor and compute deltas.
  4. 4Summarize the full day into one narrative: which deploys regressed, which improved, and the standout issues.
  5. 5Append the narrative as a dated page in the Notion regression-log database.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.