DEVOPS
Gate Vercel production promote on Lighthouse budget regression
When a Vercel deployment finishes building, runs synthetic Lighthouse checks against the preview URL and blocks the promote-to-production if performance, LCP, or bundle size…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment.succeeded webhookVercel
- LogicFilter to preview builds in READY state
- ActionRun synthetic Lighthouse audit on preview URLVercel
- LogicCompare score, LCP, transfer size to baseline budgets
- ActionPromote to production or cancel the promoteVercel
- OutputPost pass/fail metric diff to SlackSlack
What it does
Intercepts every successful Vercel preview build, runs a synthetic Lighthouse audit against the generated preview URL, and compares the scores to the production baseline budgets you set (performance score, LCP, total transfer size). If any metric regresses past its threshold, the workflow cancels the production promotion and posts the failing diff to Slack so nothing ships blind.
When to use it
Use it on customer-facing apps where a slow deploy is a real incident. It catches the regression at the preview stage, before a Chairman or engineer clicks promote, instead of after users feel it.
How it works
- 1A Vercel `deployment.succeeded` webhook fires for a new preview build.
- 2A filter confirms the target is `preview` (not already production) and the build state is READY.
- 3A synthetic check hits the preview URL and pulls Lighthouse performance score, LCP, and transfer size.
- 4A branch compares each metric to the stored baseline budget.
- 5If within budget, the deployment is promoted to production via the Vercel API; if not, the promote is cancelled.
- 6The pass or fail verdict, with the metric diff, is posted to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.