DEVOPS
Correlate origin-load spikes with the deploy that caused them
On a schedule, detects Cloudflare origin-request spikes, looks back at recent Vercel deploys.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled origin-load check
- ActionRead Cloudflare origin + cache-status metricsCloudflare
- LogicContinue only if origin load exceeds baseline
- ActionFetch recent Vercel deploy timelineVercel
- LogicRank deploys by timing match to spike
- OutputPost ranked suspect deploys to incident channelSlack
What it does
This workflow is a root-cause finder for origin overload. It periodically reads Cloudflare's origin-request and cache-status metrics, and when origin load spikes above its rolling normal, it cross-references the timeline of recent Vercel deploys to name the most likely culprit. The result is a single ranked message instead of a manual scroll through two dashboards.
When to use it
Reach for it when your origin starts taking traffic it should not and you need to know which ship caused it. It is ideal for teams that deploy often, where a cache-hit regression and an origin spike are obvious in metrics but hard to pin to a specific release.
How it works
- 1A schedule fires every few minutes.
- 2Read Cloudflare origin-request volume and cache-status breakdown for the zone.
- 3Branch: continue only if origin load exceeds the rolling baseline by the configured margin.
- 4Fetch the recent Vercel deploy timeline for the project.
- 5Score each deploy by how tightly its finish time precedes the spike onset.
- 6Post the ranked suspect deploys, with cache-status numbers, to the incident Slack channel.
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 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.