DEVOPS
Promote Vercel Bundle Baseline on Main Merge
When a PR merges to main and its production deploy succeeds, captures the new per-route bundle sizes and promotes them to the stored production baseline used by PR budget gates.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeeded on mainVercel
- LogicConfirm production target and merge commit
- ActionFetch final per-route bundle sizesVercel
- ActionUpsert sizes into baseline tablePostgres
- OutputComment baseline promotion on the commitGitHub
What it does
Keeps the bundle-size baseline honest. Every time main merges and the resulting production deploy succeeds, it records that build's per-route sizes as the new baseline, so future PR comparisons measure against what is actually live rather than a stale snapshot.
When to use it
Use it alongside a PR budget gate so the two stay in sync: the gate reads the baseline this flow writes. Run it whenever you want baseline promotion to be automatic and tied to real production deploys instead of a manual checked-in file.
How it works
- 1A Vercel production deployment-succeeded webhook fires, scoped to the main branch.
- 2A logic step confirms the deploy is the production target and corresponds to a merge commit.
- 3The flow fetches the final per-route bundle sizes from the Vercel build output.
- 4It upserts those sizes into the Postgres baseline table, replacing the prior values.
- 5It posts a short GitHub commit comment confirming the baseline was promoted, including total first-load JS for traceability.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.