ENGINEERING
Block Vercel promotion when Sentry source maps are missing
On every Vercel production deploy, confirm the matching Sentry release has uploaded artifacts and a symbolicated frame before the deploy is allowed to serve traffic.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-ready webhookVercel
- ActionFetch Sentry release + list artifacts for git SHASentry
- LogicVerify artifacts exist and sample frame symbolicates
- ActionPromote deploy to production (pass path)Vercel
- OutputPost blocking alert with missing-map details (fail path)Slack
What it does
It turns Sentry source-map verification into a hard gate on Vercel production deploys. After a build finishes, it checks that the release actually has source maps in Sentry and that a sample stack frame symbolicates to real source — not minified gibberish. If verification fails, it stops the deploy from being promoted and pings the team.
When to use it
Use it when broken source maps keep slipping into production and your on-call ends up debugging minified `a.b.c` frames during incidents. Best for teams on Vercel that already ship Sentry releases per deploy.
How it works
- 1A Vercel deployment-ready webhook fires with the deploy ID and git SHA.
- 2The flow queries Sentry for the release tied to that SHA and lists its artifacts.
- 3A logic step checks artifact count and runs a symbolication probe on a known frame.
- 4If maps are present and frames resolve, it calls Vercel to promote the deploy.
- 5If not, it skips promotion and posts a blocking alert to Slack with the release and missing-artifact details.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 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.