DEVOPS
Purge Cloudflare cache tags when CMS content is published
Triggered by a content-publish webhook, maps the published entry to its Cloudflare cache tags and purges by tag so only affected pages clear, then logs the event for audit.
How it runs
The automated pipeline, trigger to output.
- TriggerCMS publish HTTP webhookHTTP webhook
- LogicDerive cache tags from published entry
- ActionCloudflare purge-by-tagCloudflare
- LogicConfirm purge succeeded
- OutputWrite purge audit row to PostgresPostgres
What it does
When an editor publishes or updates content, this workflow purges Cloudflare by cache tag rather than by URL, so every page that embeds that content (lists, related-content blocks, the entry page itself) clears in a single call. It then writes an audit record of what was purged and by whom.
When to use it
Use it when content updates are decoupled from code deploys and the same entry appears across many cached pages. Cache tags let one edit invalidate exactly the right surface area without listing URLs by hand or purging the whole zone.
How it works
- 1An HTTP webhook receives the CMS publish event with the entry ID and type.
- 2A logic step derives the Cloudflare cache tags for that entry (for example `post-123`, `author-7`, `tag-listing`).
- 3Cloudflare purge-by-tag clears every page carrying those tags.
- 4A logic check confirms the purge response succeeded.
- 5A Postgres insert records the entry, tags purged, editor, and timestamp for the audit log.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.