ENGINEERING
Daily release-health scorecard to Notion and Slack
Each morning compiles the prior day's releases with their crash-free rates, adoption, and any gate actions into a Notion scorecard and posts a digest to Slack for the engineering…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionList trailing-24h releases with health metrics from SentrySentry
- ActionCorrelate each with Vercel promotion statusVercel
- LogicRank releases and mark health-bar misses
- ActionWrite a dated scorecard row to NotionNotion
- OutputPost a standup digest to SlackSlack
What it does
Gives the team one place to see how recent releases behaved. It rolls up yesterday's deployments with their crash-free rate, user adoption, and whether any promotion was held or rolled back.
When to use it
Use it for standup or a weekly review when you want trend visibility without logging into Sentry. Good for eng managers tracking release quality over time and keeping a written record in Notion.
How it works
- 1A daily morning schedule triggers the flow.
- 2It lists releases shipped in the trailing 24 hours from Sentry with crash-free rate, session count, and adoption.
- 3It correlates each with its Vercel deployment to note promotion or rollback status.
- 4A step ranks releases best-to-worst and marks any that missed the health bar.
- 5It writes a dated scorecard row to a Notion database with the full table.
- 6A condensed digest, highlighting any misses, posts to the engineering Slack channel for standup.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.