DEVOPS
Gate PR merge on Vercel preview performance budget
Runs a headless performance and accessibility audit against each new Vercel preview and writes a pass/fail commit status back to the GitHub PR so merges are blocked…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionAudit preview URL in headless browserBrowserbase
- LogicScores meet performance budget?
- OutputWrite pass/fail commit status to PRGitHub
What it does
Every Vercel preview gets a performance and accessibility audit in a real browser. The workflow compares the scores against your configured budget (for example, performance >= 85, accessibility >= 90) and writes a GitHub commit status check on the pull request. If the preview is too slow or fails a11y, the required check goes red and the PR cannot merge.
When to use it
Use it to enforce a performance budget as a hard merge requirement, not a suggestion. Great for marketing sites and customer-facing apps where a regression in load time or accessibility should never reach production unnoticed.
How it works
- 1Vercel fires a deployment.ready webhook for a preview tied to a PR.
- 2A headless browser loads the preview URL and captures performance and accessibility metrics.
- 3A branch compares each metric to the configured budget thresholds.
- 4The flow posts a commit status (success or failure) to the GitHub PR head SHA, with the scores in the description.
- 5The required status check then gates the merge button automatically.
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.