ActionCloudflareUpdated May 2026

What zones (domains) are on this Cloudflare account?

Short answer: Drop the "Cloudflare → List Zones" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 6 Cloudflare actions

Sample request

{}

Returns

{
  "result": [
    {
      "id": "zone123",
      "name": "example.com",
      "plan": {
        "name": "Free"
      },
      "status": "active"
    }
  ],
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for List Zones.

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 List Zones.

What does the List Zones action do in Cloudflare?

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").

What inputs does List Zones require?

List Zones has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Zones support batch operations?

Yes. Run List Zones 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