DEVOPS
Vercel Preview Browser E2E Gate
Drives a headless browser through a critical user journey on each new Vercel preview deployment, captures screenshots of every step.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- LogicFilter to preview builds on an open PR
- ActionRun scripted browser journey with screenshotsBrowserbase
- LogicFail run if any step errors or asserts false
- OutputSet commit status and post screenshot checklist to PRGitHub
What it does
Runs a real browser end-to-end flow against a fresh Vercel preview, not just an HTTP ping. Browserbase loads the preview URL, clicks through a critical journey (sign in, open dashboard, submit the core form), and screenshots each step. The pass/fail outcome and screenshot links land on the pull request so reviewers see exactly what the bot saw.
When to use it
Use it for apps where the risk lives in client-side rendering and interaction, not just status codes, such as auth flows, multi-step forms, or single-page apps where a 200 hides a broken UI.
How it works
- 1Vercel sends a deployment-succeeded webhook with the preview URL and commit SHA.
- 2A filter keeps only preview deployments attached to an open pull request.
- 3Browserbase launches a session, walks the scripted journey on the preview URL, and grabs a screenshot at each checkpoint.
- 4Logic marks the run failed if any step times out or an assertion misses.
- 5GitHub receives a commit status plus a PR comment linking the step-by-step screenshots, gating merge on a clean run.
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
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.