DEVOPS
Daily Cloudflare cache health digest with deploy annotations
Each morning, summarizes the prior day's Cloudflare cache-hit ratio and origin load per zone, annotates the timeline with Vercel deploys, and posts a readable digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionPull yesterday's Cloudflare cache analyticsCloudflare
- ActionFetch Vercel deploys from same windowVercel
- LogicCompose per-zone digest with deploy annotations
- OutputPost digest to engineering Slack channelSlack
What it does
This workflow produces a once-a-day readout of how well your edge cache served traffic. It rolls up Cloudflare cache-hit ratio, bytes saved, and origin-request volume for the previous day, overlays the Vercel deploys that happened, and writes a plain-language digest so the team can spot a slow-bleeding regression that never tripped a hard alert.
When to use it
Use it for steady operational awareness rather than incident response. It is for teams who want a morning glance at cache health, with deploy context, to catch gradual degradation and to keep cache efficiency visible to people who do not live in dashboards.
How it works
- 1A daily schedule fires each morning.
- 2Pull yesterday's Cloudflare cache analytics for each configured zone.
- 3Fetch the list of Vercel deploys from the same window to annotate the timeline.
- 4Compose a digest: per-zone cache-hit ratio, origin load trend, and which deploys landed.
- 5Post the formatted digest to the team's engineering 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.