DEVOPS
Record bundle-size baseline on default-branch merge
When a build completes on the production branch, captures the bundle size per route group and writes it to BigQuery as the new baseline future MRs are compared against.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deployment succeededVercel
- LogicKeep only default-branch deployments
- ActionGroup client bundle bytes by routeVercel
- ActionInsert baseline rows with SHA and timestampBigQuery
- OutputMark rows as active branch baselineBigQuery
What it does
When Vercel finishes a production (default-branch) build, this workflow breaks down the bundle by route group, records each size along with the commit SHA and timestamp into a BigQuery baselines table, and marks it as the current authoritative baseline. This is the data source the MR-comparison workflows read from, so baselines stay accurate as main moves forward.
When to use it
Run this as the companion to any MR bundle-budget check. It keeps your baseline honest by updating it only on merges to the default branch, so preview comparisons measure against what actually shipped rather than a stale snapshot.
How it works
- 1Vercel `deployment.succeeded` webhook fires for a production build.
- 2Filter to deployments whose target is the default branch; ignore all others.
- 3Pull build output and group client bundle bytes by route segment.
- 4Insert one baseline row per route group with size, commit SHA, and timestamp into BigQuery.
- 5Mark the inserted rows as the active baseline for that branch.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.