DEVOPS
Failed Deploy to Auto-Rollback and On-Call Page
When a Vercel deployment fails or its post-deploy health check breaks, page on-call in PagerDuty, open a GitHub revert PR for the bad commit, and notify the team in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment failedVercel
- LogicFilter to production target failures only
- ActionPage deploy on-call via PagerDutyPagerDuty
- ActionOpen GitHub revert PR for the bad commitGitHub
- OutputNotify team in Slack with rollback linkSlack
What it does
Reacts to a broken deployment before it lingers in production. When a Vercel deploy errors or its health check fails, it pages the on-call engineer, drafts a GitHub revert PR for the offending commit so a fix is one click away, and posts the deploy failure context to Slack.
When to use it
Use it when bad deploys need an immediate human and a ready rollback path, especially for services where a failed release should never sit unattended.
How it works
- 1A Vercel deployment event reports an `error` or `failed` state.
- 2Logic checks whether the failure is on a production target; preview failures are ignored.
- 3A PagerDuty incident is created to page the deploy on-call rotation with the build logs link.
- 4GitHub opens a revert PR against the failing commit on the production branch, ready to merge.
- 5A Slack message reports the failed deploy, the page, and a link to the prepared revert PR for fast rollback.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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 DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.