ENGINEERING
Nightly audit of production releases for missing source maps
Runs each night across all production Sentry releases from the last 24 hours, flags any release missing artifacts or producing unsymbolicated events.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionList production releases from last 24hSentry
- LogicClassify each release healthy vs broken maps
- ActionFile Linear issue per broken releaseLinear
- OutputPost nightly healthy/broken digestSlack
What it does
It sweeps your recent production Sentry releases every night and finds the ones that are silently broken — no uploaded artifacts, or live events still showing minified frames. For each one it opens a tracked ticket so nothing rots unnoticed between deploys.
When to use it
Use it as a safety net behind your deploy-time gate. Even with checks in CI, drift happens (rotated tokens, changed bundlers, edge functions). This catches what slipped through, on a schedule.
How it works
- 1A nightly schedule trigger fires at a fixed hour.
- 2The flow pulls all production releases created in the last 24 hours from Sentry.
- 3For each release it lists artifacts and samples recent events for unsymbolicated frames.
- 4A logic step classifies each release as healthy or broken with a reason.
- 5For every broken release it creates a Linear issue tagged with the release and root-cause hint.
- 6It posts a one-line nightly digest to Slack with the healthy/broken counts.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.