DEVOPS
Daily Vercel bandwidth burn-rate digest with month-end projection
Each morning pulls yesterday's Vercel bandwidth and image-optimization usage, projects month-end spend against your plan's included quota.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled run after midnight UTC
- ActionFetch yesterday's bandwidth usage per projectVercel
- LogicProject month-end spend and assign status color
- ActionLog daily usage snapshot for trendsAxiom
- OutputPost ranked burn-rate digest to SlackSlack
What it does
Gives the team a once-a-day read on how fast they are spending Vercel bandwidth. It pulls usage for the prior day, compares the month-to-date burn against the included quota, projects where the month will land, and ranks the projects driving the spend.
When to use it
Use it when bandwidth overages surprise you at billing time. A daily projection lets you catch an unoptimized asset or a leaked preview URL while there is still time to act, rather than after the overage lands.
How it works
- 1A scheduled trigger runs every morning after midnight UTC.
- 2The flow queries the Vercel usage API for yesterday's bandwidth and image-optimization totals per project.
- 3It pulls month-to-date usage and computes a linear month-end projection against the plan quota.
- 4A logic step tags the run green, amber, or red based on how the projection compares to quota.
- 5It logs the daily snapshot to Axiom so trend history is queryable.
- 6It posts a Slack digest with the burn rate, projection, status color, and the top five projects by bandwidth.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.