DEVOPS
Gate PR merges on preview-deploy error budget health
When a Vercel preview deploy is ready for a pull request, it runs synthetic traffic, checks Sentry for new errors on that preview release.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment ready for PRVercel
- ActionSend synthetic traffic to the preview URLHTTP webhook
- ActionQuery Sentry for new issues on preview releaseSentry
- LogicDecide pass/fail on new errors
- ActionPost commit status check to GitHub PRGitHub
- OutputComment offending issues on the PR if failedGitHub
What it does
Stops regressions before they reach production by error-budget-testing the preview build. When a PR's Vercel preview deployment is ready, the flow exercises it, queries Sentry for any new issues tagged to that preview release, and reports a pass or fail back to the pull request as a commit status, blocking merge if the preview introduces fresh errors.
When to use it
Use it when you want error regressions caught at the PR stage instead of after production rollout, giving reviewers a reliability signal alongside CI and tests.
How it works
- 1A Vercel preview-deployment-ready webhook fires with the PR and preview URL.
- 2The flow sends synthetic requests to the preview URL to generate traffic.
- 3It queries Sentry for new issues attributed to the preview release.
- 4A branch decides pass or fail based on whether new errors appeared.
- 5It posts a commit status check back to the GitHub pull request.
- 6On failure it comments on the PR with the offending issues.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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
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-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.