DEVOPS
Nightly Lighthouse trend audit of latest Vercel preview into GitLab
On a nightly schedule, finds the most recent Vercel preview for the active branch, runs a multi-page Lighthouse audit, appends the scores to a tracked trend file in the repo.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionResolve latest Vercel preview URLVercel
- ActionRun multi-page Lighthouse auditShell
- ActionAppend record, compute rolling averageShell
- ActionCommit trend file to GitLab repoGitLab
- OutputSummarize scores vs rolling average
What it does
Provides a continuous, time-series view of preview quality rather than a per-commit gate. Each night it audits the latest preview across several key pages, records the scores, and commits the rolling history to the repository so trends are visible in GitLab.
When to use it
Use it alongside the per-MR gate when you want to spot slow erosion that no single MR triggers, or to produce weekly quality reports. Good for teams reporting QA health to stakeholders.
How it works
- 1A schedule trigger fires nightly.
- 2A Vercel action resolves the most recent preview deployment URL for the tracked branch.
- 3A shell step runs Lighthouse across the configured page set and emits a dated record.
- 4A shell step appends the record to the trend file and computes a rolling average.
- 5A GitLab action commits the updated trend file to the repo.
- 6The job outputs a short summary of last night's scores versus the rolling average.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.