ENGINEERING
Escalate a severe crash-free regression to PagerDuty and flag rollback on Vercel
When a new Sentry release's crash-free rate falls far below baseline, opens a PagerDuty incident for the on-call and posts an urgent rollback-recommended comment on the Vercel…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release-health event for new deploySentry
- ActionFetch new vs baseline crash-free rateSentry
- LogicCheck drop against severe rollback threshold
- ActionOpen PagerDuty incident for release on-callPagerDuty
- OutputPost urgent rollback comment on Vercel deploymentVercel
What it does
Handles the serious case, not the borderline one. This workflow watches new Sentry releases and reacts only when the crash-free rate drops sharply below baseline, past a severe threshold. At that point it pages the on-call through PagerDuty and posts an urgent comment on the Vercel deployment recommending immediate rollback, so a bad release gets human eyes within minutes.
When to use it
Use it as the high-severity tier of your release gate, separate from routine promote/hold logic. Reserve it for regressions big enough to warrant waking someone, so PagerDuty stays meaningful and the rollback signal isn't lost in chat.
How it works
- 1Sentry emits a release-health event for the new deploy.
- 2The flow fetches the new release's crash-free rate and the baseline from Sentry.
- 3A logic step checks whether the drop crosses the severe rollback threshold.
- 4If it does, it triggers a PagerDuty incident routed to the release on-call.
- 5It posts an urgent rollback-recommended comment on the Vercel deployment with the crash-free figures attached.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect VercelDeploys, runtime logs, analytics.
- 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.