DEVOPS
Nightly Lighthouse trend on the staging Vercel alias
On a nightly schedule, audits the current Vercel staging alias with Lighthouse, writes the scores to BigQuery for trend tracking.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionResolve current Vercel staging aliasVercel
- ActionRun Lighthouse audit on stagingBrowserbase
- ActionAppend scores to BigQuery trend tableBigQuery
- LogicCheck rolling budget
- OutputPage on-call via PagerDuty on failurePagerDuty
What it does
This runs the QA gate on a cadence rather than per-deploy. Each night it audits whatever is currently promoted to the staging alias, appends the scores to a BigQuery table for long-term trend analysis, and raises a PagerDuty incident if the build has drifted below your rolling budget since the last green night.
When to use it
Use this when you want to catch slow performance decay that no single PR triggers, such as growing bundle size or third-party script creep. The BigQuery history powers dashboards and the PagerDuty hook ensures regressions get owned overnight, not discovered by users.
How it works
- 1A nightly schedule fires the workflow.
- 2An action resolves the current Vercel staging alias URL.
- 3A Lighthouse run audits the alias and captures full category scores and metrics.
- 4The scores are appended to a BigQuery table keyed by date and commit.
- 5A logic step compares against the rolling budget; if it fails, a PagerDuty incident is created with the metric breakdown.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.