DEVOPS
Vercel Preview Error-Watch Rollup Gate
After a Vercel preview deploys, exercises the preview with smoke traffic, watches Sentry for new errors triggered against that release.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- ActionDrive smoke traffic across preview routesHTTP webhook
- ActionQuery Sentry for issues on this releaseSentry
- LogicPass/fail on presence of new errors
- OutputPost error rollup and set error-watch commit statusGitHub
What it does
Catches runtime errors a preview only surfaces under traffic. The workflow pings the preview's main routes to generate activity, waits a short window, then queries Sentry for issues tagged to that preview release. Any new, unresolved errors become a blocking PR comment listing the exception, count, and stack link so the author can fix before merge.
When to use it
Use it when build-green and smoke-200 still let runtime exceptions slip through, especially for code paths that only throw when actually invoked. Requires Sentry releases tagged with the preview's commit SHA.
How it works
- 1Vercel sends a deployment-succeeded webhook for a preview build with its commit SHA.
- 2An HTTP step drives smoke traffic across the preview's key routes.
- 3Sentry is queried for issues scoped to the matching release after a short settle window.
- 4Logic decides pass or fail based on whether any new unresolved errors exist.
- 5GitHub gets an `error-watch` commit status and, on failure, a rollup comment of the new exceptions with links into Sentry.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SentryErrors, performance, releases.
- 4Connect GitHubRepos, issues, pull requests, 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
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.