DEVOPS
Escalate sudden Vercel spend spikes to on-call via PagerDuty
Runs hourly to detect when Vercel build or bandwidth spend jumps sharply above its recent baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly scheduled spend check
- ActionPull current-hour build and bandwidth spendVercel
- ActionRead trailing baseline samplesAxiom
- LogicDoes spend deviation clear the spike threshold?
- ActionOpen PagerDuty incident for on-callPagerDuty
- OutputRecord spike sample to baseline storeAxiom
What it does
Catches Vercel cost spikes the moment they start instead of at month end. Every hour it compares the latest spend rate against a recent baseline, and a sharp deviation opens a PagerDuty incident routed to the on-call engineer.
When to use it
Use it for the failure modes that move fast: a hot-looping deploy bot, a viral page hammering bandwidth, or an image-optimization misconfiguration. These can spend a meaningful chunk of budget in hours, faster than a daily digest would surface.
How it works
- 1An hourly scheduled trigger starts the check.
- 2The flow pulls the current hour's build and bandwidth spend from the Vercel usage API.
- 3It reads the trailing baseline from Axiom and computes the deviation from normal.
- 4A logic step decides whether the spike clears the alert threshold; if not, it records the sample and exits quietly.
- 5On a confirmed spike it opens a PagerDuty incident tagged with the top contributing projects and the spend delta.
- 6It writes the spike sample back to Axiom so the baseline stays current.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.