SUMMARIZATION

Weekly Sentry regression-trend brief to MS Teams

Every Monday, compares the past week's Sentry releases to the prior week and posts a trend brief to Microsoft Teams highlighting recurring error signatures and whether overall…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday morning schedule
  • ActionQuery this week vs. last week releasesSentrySentry
  • ActionCompute trend and summarize recurring signaturesOpenAI
  • OutputPost trend brief to MS TeamsMicrosoft Teams

What it does

This workflow gives leadership a weekly health trend rather than per-deploy detail. Each Monday it pulls the last week of Sentry releases, compares aggregate crash-free rate and recurring signatures against the prior week, and posts a short trend brief to a Microsoft Teams channel stating whether release health is improving, flat, or regressing.

When to use it

Use it for an engineering-leadership cadence where the question is direction, not individual incidents. It complements the daily Slack rollup by zooming out to week-over-week movement.

How it works

  1. 1A Monday-morning schedule triggers the run.
  2. 2The flow queries Sentry for this week's and last week's releases, crash-free rates, and top recurring signatures.
  3. 3An OpenAI step computes the week-over-week delta and writes a trend brief calling out signatures that keep returning.
  4. 4The brief is posted to the chosen Microsoft Teams channel with a clear improving/flat/regressing headline.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  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.