DEVOPS
Nightly Production Bundle-Size Trend Report
On a nightly schedule, records the production deployment's bundle sizes to a time-series table and emails a trend report flagging routes that have crept upward over the trailing…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionFetch production bundle statsVercel
- ActionAppend measurements to history tablePostgres
- LogicCompute 14-day per-route growth
- OutputEmail trend report to eng leadGmail
What it does
Tracks slow bundle creep that per-PR gates miss. Each night it captures the current production build's per-route bundle sizes, appends them to a history table, and produces a trend report highlighting any route that grew more than your tolerance over the last 14 days, then emails it to the engineering lead.
When to use it
Use it when individual PRs each stay under budget but the app keeps getting heavier month over month. This gives you the long-range view and an early warning before a route blows its budget.
How it works
- 1A nightly schedule triggers the run.
- 2The flow fetches the latest production deployment's bundle stats from Vercel.
- 3It inserts today's measurements into a Postgres time-series table.
- 4A logic step queries the trailing 14-day window and computes per-route growth.
- 5It flags routes exceeding the creep tolerance.
- 6An email goes to the engineering lead with the ranked growth table and sparkline data.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GmailRead, draft, send, label.
- 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
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.