ActionCloudflareUpdated September 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.

Purge Cloudflare Cache in Cloudflare — start free All 6 Cloudflare actions

Purge Cloudflare Cache in Cloudflare — start free

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Zone ID zoneId	string	Required	Zone ID
Purge Everything purge_everything	boolean	Optional	Purge 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.

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 run history shows the failed step with its input and the error message Cloudflare returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Purge Cloudflare Cache support batch operations?

Run Purge Cloudflare Cache inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Cloudflare's rate limits.

More actions