ENGINEERING
Post-deploy Vercel error watch with rollback alert
After a Vercel production deploy, waits a few minutes then checks Sentry for a release-over-release error spike; if errors jumped, it pings the deployer in Slack with a one-click…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deployment succeedsVercel
- LogicWait a bake period, then compare release error rates
- ActionQuery Sentry for new-vs-prior release error countsSentry
- LogicBranch on whether the spike exceeds threshold
- ActionDM the deployer in Slack with diff and rollback promptSlack
- OutputFile a Linear bug tagged to the bad releaseLinear
What it does
Guards every production deploy by comparing the new release's error rate against the previous one shortly after it ships, then alerts the person who deployed and creates a tracked bug if the release made things worse.
When to use it
Use it when you deploy frequently on Vercel and want a fast safety net that catches bad releases before users do, without staring at dashboards after each push. Best when releases are tagged in Sentry.
How it works
- 1Vercel's deployment-succeeded webhook fires for a production deploy and supplies the release identifier.
- 2The flow waits a short bake period to let real traffic exercise the new release.
- 3It queries Sentry comparing error counts for the new release versus the prior one.
- 4A logic step decides whether the increase exceeds the spike threshold.
- 5If it does, Slack DMs the deployer with the diff and a rollback prompt, and a Linear bug is filed tagged to the release.
- 6If not, the run ends quietly with no noise.
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.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.