AI AGENTS
Combined Cloudflare + Vercel weekly bill reconciler
Each week an agent pulls usage and cost from both Cloudflare and Vercel, attributes the week's overage to the single largest cost driver across both platforms.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled reconciliation
- ActionFetch weekly Cloudflare usage and cache ratioCloudflare
- ActionFetch weekly Vercel usageVercel
- LogicNormalize to cost and compute deltas
- ActionIdentify top driver and prioritized fixOpenAI
- OutputWrite reconciled report to NotionNotion
What it does
Reconciles spend across your two edge platforms in one pass. It gathers Cloudflare bandwidth/requests and Vercel compute/invocations for the week, normalizes them into cost contribution, and names the single biggest driver of the week's overage along with the highest-leverage fix.
When to use it
When your infra bill is split between Cloudflare and Vercel and you want one weekly artifact that says where the money actually went and what to fix first, instead of two separate dashboards.
How it works
- 1A weekly schedule kicks off the reconciliation.
- 2The agent fetches Cloudflare analytics (bandwidth, requests, cache ratio) for the week.
- 3In parallel it fetches Vercel usage (invocations, duration, bandwidth) for the same window.
- 4A logic step normalizes both into estimated cost and computes week-over-week deltas.
- 5An OpenAI step identifies the top cross-platform driver and the single prioritized remediation.
- 6The reconciled report is written to a Notion page for the team's weekly review.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.