SUMMARIZATION

Daily Sentry release-health digest across deploys

Each morning it rolls up every production release shipped in the last 24 hours, ranks them by error-rate change.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionList production releases from the last 24hVercelVercel
  • ActionFetch release-health + new-issue counts per releaseSentrySentry
  • LogicRank by error-rate delta; flag net-new issues
  • ActionCompose ranked daily reliability digestOpenAI
  • OutputEmail digest to engineering listGmailGmail

What it does

Once a day it gathers all releases deployed in the past 24 hours, fetches each one's Sentry release-health metrics, and produces a ranked digest: which deploys cut error rate, which raised it, and which introduced brand-new issues. Instead of per-deploy noise, the team gets one readable trend summary over breakfast.

When to use it

Use it when leads want a calm daily reliability pulse rather than real-time alerts, or to spot slow regressions that accumulate across many small deploys.

How it works

  1. 1A scheduled trigger runs every morning.
  2. 2The flow lists production releases from the last 24 hours via Vercel.
  3. 3Sentry returns release-health and new-issue counts for each release.
  4. 4A logic step ranks releases by error-rate delta and flags net-new issues.
  5. 5An OpenAI step composes a digest with a one-line verdict per release and an overall trend note.
  6. 6The digest is emailed to the engineering distribution list.

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 GmailRead, draft, send, label.
  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.