DEVOPS
Block Vercel promotion when Lighthouse budgets fail
When a Vercel preview deployment finishes, runs Lighthouse against the preview URL and blocks promotion to production if any performance, accessibility, or SEO budget is breached.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse audit on preview URLBrowserbase
- LogicCompare scores to budget thresholds
- ActionTag deployment promotable or held in VercelVercel
- OutputPost pass/fail verdict to SlackSlack
What it does
Every Vercel preview deploy is automatically scored against a Lighthouse budget you define. If the build clears every threshold it is marked promotable; if any category falls short, the workflow flags the deployment as blocked and reports the exact failing metrics to your release channel so nobody ships a regression by accident.
When to use it
Use this when your team treats Vercel previews as the last gate before production and you want an objective, repeatable performance bar instead of eyeballing PageSpeed. Ideal for marketing sites and dashboards where Core Web Vitals directly affect conversion or SEO.
How it works
- 1A Vercel deployment-ready webhook fires with the preview URL and commit SHA.
- 2A Lighthouse run (headless Chrome) audits the preview URL for performance, accessibility, best-practices, and SEO scores.
- 3A logic step compares each score against the configured budget thresholds.
- 4If all pass, the deployment is tagged promotable in Vercel; if any fail, promotion is held.
- 5A Slack message posts the pass/fail verdict, the failing categories, and a link to the full report.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.