DEVOPS
Block Vercel promotion when preview smoke checks fail
On every Vercel preview deployment, runs scripted browser smoke checks against the critical paths and posts a pass/fail gate to the PR so a broken preview can't be promoted…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeeded webhookVercel
- LogicFilter to preview-environment success events
- ActionRun scripted critical-path smoke checks in headless browserBrowserbase
- LogicAggregate path results into pass or fail
- ActionSet GitHub commit status qa/smoke on the PRGitHub
- OutputComment pass/fail with failing path and screenshot on PRGitHub
What it does
Every time Vercel finishes a preview deployment, this workflow drives a headless browser through your critical user paths (load homepage, sign in, reach checkout) against the fresh preview URL. If any path breaks, it marks the GitHub commit status red and comments the failure so the deploy can't be promoted.
When to use it
Use it when broken previews keep slipping to production because review is manual. It gives every PR an automatic, deterministic quality gate tied to the exact preview build.
How it works
- 1Vercel fires a deployment webhook carrying the preview URL and commit SHA.
- 2A filter passes only `deployment.succeeded` events targeting the preview environment.
- 3Browserbase opens the preview URL and walks each scripted critical path, capturing screenshots and assertions.
- 4A logic step aggregates results into pass or fail.
- 5The workflow sets a GitHub commit status (`qa/smoke`) and posts a PR comment with the screenshot and which path failed.
- 6On pass it sets the status green so promotion is unblocked.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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 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.