DEVOPS
Weekly bundle-size trend digest to Slack
On a weekly schedule, queries BigQuery for bundle-size baselines over the past period and posts a Slack digest showing per-route growth, the biggest gainers, and the overall trend.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery trailing-window baselinesBigQuery
- LogicRank top gainers and shrinkers
- ActionFormat trend digest
- OutputPost digest to Slack channelSlack
What it does
Once a week this workflow reads the accumulated bundle-size baselines from BigQuery, computes how each route group changed over the trailing window, ranks the largest gainers, and posts a readable digest to a Slack channel. Engineers get a regular, low-effort view of where the app is quietly getting heavier over time.
When to use it
Use it when per-MR checks catch single regressions but you still want the longer-term picture: slow creep across many small MRs that no individual check would flag. Good for a Monday platform-health channel post.
How it works
- 1A weekly schedule triggers the run.
- 2Query BigQuery for baseline rows across the trailing window, grouped by route.
- 3Compute week-over-week delta per route and rank the top gainers and shrinkers.
- 4Format a digest with totals, top movers, and an overall trend line.
- 5Post the digest to the configured Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.