DEVOPS
Purge Cloudflare cache when a Vercel production deploy succeeds
Listens for Vercel's deployment.succeeded webhook on the production target and triggers a full Cloudflare zone cache purge, then posts the result to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment.succeeded webhookVercel
- LogicOnly continue if target is production
- ActionCloudflare purge_everything for the zoneCloudflare
- LogicVerify purge response success
- OutputPost purge confirmation to SlackSlack
What it does
When a Vercel production deployment finishes successfully, this workflow immediately purges the entire Cloudflare cache for your zone so visitors get the freshly deployed assets instead of stale cached HTML and JavaScript. It confirms the purge in Slack with the deploy URL and commit.
When to use it
Use it when your site sits behind Cloudflare in front of Vercel and you want zero manual steps between shipping and serving fresh content. Ideal for marketing sites and dashboards where a stale edge cache after deploy is a recurring support complaint.
How it works
- 1A Vercel webhook fires on `deployment.succeeded`.
- 2A logic step checks `target == production` and ignores preview and staging deploys.
- 3Cloudflare's purge_everything call clears the whole zone cache.
- 4The workflow reads back the purge response to confirm a `success: true` body.
- 5A Slack message reports the zone, commit SHA, deploy URL, and purge status to the 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.