Purge Cloudflare Cache: Cloudflare action

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.

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. Tiny Command handles Cloudflare's rate limits automatically so you don't have to throttle manually.

More actions