DEVOPS
Nightly audit of the live Vercel production build with Slack digest
On a nightly schedule, audits the current Vercel production deployment with Lighthouse and a Honeycomb health pull, then sends a single Slack digest summarizing scores, trends…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionGet current production deploymentVercel
- ActionRun Lighthouse on production URLShell
- ActionPull 24h health stats from HoneycombHoneycomb
- LogicFlag any threshold breaches
- OutputPost production health digest to SlackSlack
What it does
This workflow keeps a steady pulse on what is actually live in production. Each night it identifies the current Vercel production deployment, runs a Lighthouse audit against the production URL, pulls 24-hour error and latency stats from Honeycomb, and rolls everything into one readable digest posted to Slack so the team starts the day knowing the state of prod.
When to use it
Use it as an ongoing health report independent of deploy events — useful for catching slow drift in performance or reliability that no single PR gate would flag.
How it works
- 1A nightly schedule trigger fires the run.
- 2An action queries the Vercel API for the current production deployment and its URL.
- 3A shell step runs Lighthouse against the production URL and captures scores.
- 4An action pulls the last 24 hours of error rate and p95 latency from Honeycomb.
- 5A logic step compares both against thresholds and flags any breaches.
- 6An output step posts a formatted Slack digest with scores, telemetry, and flagged items to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect HoneycombDistributed traces and queries.
- 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.