DEVOPS
Batch-audit key routes on a Vercel preview before promotion
Runs Lighthouse across a list of critical routes on a Vercel preview, aggregates the worst scores, and blocks promotion if any single route breaches budget.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse on each critical routeBrowserbase
- LogicAggregate worst score per category
- ActionMark deployment promotable or heldVercel
- OutputPost per-route scorecard to TeamsMicrosoft Teams
What it does
A homepage that passes Lighthouse can hide a checkout page that fails. This workflow audits a configured set of critical routes on the preview, not just the root URL, and treats the gate as failed if any one route breaches its budget. It posts a per-route scorecard so you see exactly which page dragged the build down.
When to use it
Use this for multi-page apps where different routes have different risk profiles, like landing pages, pricing, and the signup flow. It prevents a green root-URL check from masking a slow but business-critical page.
How it works
- 1A Vercel deployment-ready webhook fires with the preview base URL.
- 2An action expands the configured route list and runs a Lighthouse audit for each route.
- 3A logic step aggregates results and finds the worst-performing route per category.
- 4If every route clears budget, the deployment is marked promotable in Vercel; if any route fails, promotion is held.
- 5A Microsoft Teams card posts the per-route scorecard with the failing routes highlighted.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.