DEVOPS
Fail the gate when a preview exceeds its performance budget
On each Vercel preview deploy, measures load time and key web-vitals on critical pages in a real browser and blocks the PR's gate status when any page breaches the configured…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionMeasure load timing and web-vitals on critical pagesBrowserbase
- LogicCompare metrics to performance budget thresholds
- ActionSet qa/perf GitHub commit statusGitHub
- OutputReport breaches and deltas to SlackSlack
What it does
This workflow enforces a performance budget per preview. After a preview deploys it loads each critical page in a real browser, captures timing and web-vitals (LCP, total blocking time, page weight), and compares them to thresholds. Breaches flip the PR gate to failing.
When to use it
Use it when performance regressions sneak in unnoticed and you want a hard budget enforced before merge rather than discovered after launch.
How it works
- 1Vercel's deployment-succeeded webhook supplies the preview URL and commit.
- 2Browserbase loads each configured critical page and collects load timing and web-vitals metrics.
- 3A logic step compares each metric to its budget threshold and flags breaches.
- 4If all pages are within budget, a green `qa/perf` commit status is set.
- 5If any page breaches, the `qa/perf` status is set failing.
- 6A Slack message reports the breached page, the offending metric, and its delta over budget.
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.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.