DEVOPS
Flag preview deploys whose edge-function cost regresses
When a Vercel preview deploy finishes, pulls edge-function invocation and compute metrics from Datadog, projects the monthly cost.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deploy succeededVercel
- ActionQuery Datadog edge-function metrics for deployDatadog
- LogicProject monthly cost vs budget ceiling
- ActionPage on-call via PagerDuty if over budgetPagerDuty
- OutputSet GitHub deployment cost statusGitHub
What it does
This catches cost regressions before they merge, not after the invoice arrives. When a Vercel preview deployment succeeds, the flow reads the edge-function execution metrics that Datadog has collected for that deployment, projects them to a monthly run-rate, and compares against your cost budget. If the new code would meaningfully raise edge spend, it fails the deploy's GitHub check and pages the on-call engineer.
When to use it
Use it when edge or serverless function cost is a real line item and a single bad change (an N+1 fetch, an uncached call) can quietly multiply invocations. It turns cost from a monthly surprise into a per-PR signal.
How it works
- 1A Vercel deployment.succeeded webhook fires for a preview deploy.
- 2An action queries Datadog for invocation count and compute duration tagged to that deployment.
- 3A logic step projects monthly cost and compares it to the configured budget ceiling.
- 4If over budget, the flow opens a PagerDuty incident for on-call review.
- 5It then sets a failing or passing GitHub deployment status so the PR reflects the cost verdict.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.