DEVOPS
Block Vercel promotion until Lighthouse budgets pass
When a Vercel preview deployment finishes, runs Lighthouse against the preview URL and only promotes the build to production if performance, accessibility, and SEO scores clear…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse audit on preview URLShell
- LogicAll category scores meet budgets?
- ActionPromote deployment to productionVercel
- OutputPost failing scores to SlackSlack
What it does
This workflow turns every Vercel preview deploy into a hard quality gate. As soon as a preview is ready, it audits the live preview URL with Lighthouse, compares each category score against thresholds you set, and decides whether the build is allowed to be promoted to production. Failing builds are stopped and the offending scores are reported so the author can fix them before they ship.
When to use it
Use it when you want objective, automatic performance and accessibility enforcement on a Next.js or static site hosted on Vercel, instead of relying on developers to remember to run Lighthouse by hand.
How it works
- 1A Vercel deployment-ready webhook fires with the preview URL and deployment ID.
- 2A shell step runs Lighthouse CI against the preview URL and emits the category scores as JSON.
- 3A logic branch checks each score (performance, accessibility, best-practices, SEO) against your minimums.
- 4If all pass, an action calls the Vercel API to promote the deployment to production.
- 5If any fail, a Slack message reports the failing categories, scores, and preview link to the channel — the build stays unpromoted.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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.