DEVOPS
Gate Vercel promotion on post-deploy Cloudflare cache-hit ratio
After a Vercel deploy finishes, watches the Cloudflare cache-hit ratio for a few minutes and either promotes the deployment to production or holds it and alerts when the ratio…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionSnapshot baseline cache-hit ratioCloudflare
- ActionRe-sample ratio after bake windowCloudflare
- LogicBranch on cache-hit ratio delta vs threshold
- ActionPromote deployment to productionVercel
- OutputPost hold + comparison to release channelSlack
What it does
This workflow turns a Vercel deploy into a guarded promotion. When a preview build finishes, it samples Cloudflare's cache-hit ratio across a short bake window, compares it to the pre-deploy baseline, and only promotes the build to production if cache performance held. A regression holds the deploy and pages the on-call engineer instead of silently shipping a cache-busting change.
When to use it
Use it when a bad cache key, header change, or routing rule can quietly drop your cache-hit ratio and hammer origin. It is for teams practicing progressive delivery who want an automatic, measurable gate between "built" and "live" rather than eyeballing dashboards after every push.
How it works
- 1A Vercel deployment-succeeded webhook fires for the preview build.
- 2Pull the current Cloudflare cache-hit ratio for the zone as a baseline snapshot.
- 3Wait out a bake window, then re-sample the ratio over the deploy's traffic.
- 4Branch: if the post-deploy ratio dropped more than the allowed delta, route to hold; otherwise route to promote.
- 5On pass, call Vercel to promote the deployment to production.
- 6On fail, post the comparison and a hold notice to the team's Slack release channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.