Start free
ActionCloudflareUpdated June 2026

How do I purge Cloudflare's edge cache?

Short answer: You can purge cloudflare cache in Cloudflare by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cloudflare Purge Cloudflare Cache action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 6 Cloudflare actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Zone ID
zoneId
stringRequiredZone ID
Purge Everything
purge_everything
booleanOptionalPurge Everything
Sample request
{
  "zoneId": "{{trigger.zoneId}}",
  "purge_everything": "{{trigger.purge_everything}}"
}
Returns
{
  "result": {
    "id": "purge123"
  },
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Purge Cloudflare Cache.

Any of these apps can fire this action as part of a workflow.

Gmail → Cloudflare
1 Gmail triggers
Slack → Cloudflare
13 Slack triggers
Google Sheets → Cloudflare
2 Google Sheets triggers
HubSpot → Cloudflare
18 HubSpot triggers
FAQ

Questions about Purge Cloudflare Cache.

What does the Purge Cloudflare Cache action do in Cloudflare?
Purges cached content by URL (up to 30 per call), by tag (Enterprise tier), or by hostname. Most app-deploy workflows do URL-based purges scoped to the changed assets to avoid edge-cache stampedes on a full purge.
What inputs does Purge Cloudflare Cache require?
Required: Zone ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Cloudflare returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Purge Cloudflare Cache support batch operations?
Yes. Run Purge Cloudflare Cache inside a Loop node to process arrays. TinyCommand handles Cloudflare's rate limits automatically so you don't have to throttle manually.
More actions

Other Cloudflare actions.

Action
Create DNS Record
Creates an A, AAAA, CNAME, TXT, MX, or other DNS record on a Cloudflare zone with optional proxied flag for routing through Cloudflare's edge. For "deploy created new subdomain → auto-create DNS record" infrastructure-as-workflow patterns.
Action
Delete DNS Record
Removes a specific DNS record by ID. Irreversible. For "service decommissioned → clean up the DNS record" workflows or for deploy-rollback automation that removes records added by a failed deploy.
Action
List DNS Records
Returns paginated DNS records on a zone with filters by type, name, content. Useful for DNS audits, for "find the IP this CNAME points to" lookups, or for backup workflows that snapshot DNS state daily.
Action
List Zones
Returns every zone (each Cloudflare-managed domain) with name, status, plan. Useful for multi-domain organisations running cross-zone operations (e.g., "purge cache on all production zones simultaneously").
Action
Update DNS Record
Updates a DNS record's content, TTL, or proxied flag. Useful for "service migrated to new IP → update A record" deploy automation or for failover-routing workflows that toggle DNS pointing.