DEVOPS
Vercel bundle-size delta to GitLab MR with trend
On every Vercel preview deploy, compares the build's bundle size against the target branch baseline and posts a delta-with-trend comment on the matching GitLab merge request.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- ActionSum client bundle bytes from build outputVercel
- ActionFetch target-branch baseline sizeBigQuery
- LogicCompute byte/percent delta and trend marker
- ActionResolve open MR for the branchGitLab
- OutputPost delta-with-trend comment on the MRGitLab
What it does
Each time Vercel finishes a preview build for a branch, this workflow measures the produced JavaScript bundle size, looks up the baseline size for the merge request's target branch, computes the byte and percentage delta, and posts a comment on the open GitLab MR. The comment shows the current size, the change versus baseline, and an arrow trend so reviewers see budget impact without leaving the MR.
When to use it
Use it when your app deploys previews on Vercel and reviews merge requests in GitLab, and you want bundle-size accountability enforced inline on every MR instead of in a separate dashboard nobody checks.
How it works
- 1Vercel `deployment.succeeded` webhook fires for a preview build.
- 2Read the deployment's build output and sum the client bundle bytes via the Vercel API.
- 3Query BigQuery for the stored baseline size of the MR target branch.
- 4Compute absolute and percent delta and pick an up/down/flat trend marker.
- 5Find the open GitLab MR for the source branch.
- 6Post or update a comment on the MR with size, delta, and trend.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.