DEVOPS
Purge only the Cloudflare URLs changed in a Vercel deploy
On a successful production deploy, diffs the deployed commit to find changed pages and assets, then issues a surgical Cloudflare purge of just those URLs instead of the whole zone.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeededVercel
- Actiongit diff changed files vs previous SHAShell
- LogicMap changed paths to public URLs
- ActionCloudflare purge-by-URL in batchesCloudflare
- OutputSlack summary of purged URLsSlack
What it does
Instead of nuking the entire edge cache on every release, this workflow inspects the commit behind a Vercel production deploy, maps changed files to their public URLs, and purges only those specific URLs from Cloudflare. Most cached traffic stays warm, so you keep cache hit rates high while still shipping fresh content.
When to use it
Reach for it on high-traffic sites where a full purge causes an origin-load spike or a noticeable latency cliff. It is built for teams that deploy frequently and cannot afford to cold-start their entire edge cache several times a day.
How it works
- 1A Vercel `deployment.succeeded` webhook fires for production.
- 2A shell step runs `git diff --name-only` against the previous deployed SHA to list changed files.
- 3A logic step maps file paths to public URLs and drops files that do not affect cached output.
- 4Cloudflare's purge-by-URL call clears just that URL batch (chunked to the API limit).
- 5A Slack note lists the exact URLs purged and the count.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.