ActionCloudflareUpdated September 2026

How do I list DNS records on a Cloudflare zone?

Short answer: You can list dns records in Cloudflare by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cloudflare List DNS Records action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List DNS Records in Cloudflare — start free All 6 Cloudflare actions

List DNS Records 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 zone_id	string	Required	Zone ID. Example: 023e105f4ecef8ad9ca31a8372d0c353
Record Type type	options	Optional	Record Type. Options: All, A, AAAA, CNAME, MX, TXT, NS
Name Filter name	string	Optional	Filter by record name

Sample request

{
  "zone_id": "e.g. 023e105f4ecef8ad9ca31a8372d0c353",
  "type": "{{trigger.type}}",
  "name": "e.g. www.example.com"
}

Returns

{
  "result": [
    {
      "id": "rec123",
      "ttl": 1,
      "name": "www.example.com",
      "type": "A",
      "content": "192.0.2.1",
      "proxied": true
    }
  ],
  "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 DNS Records.

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 DNS Records.

What does the List DNS Records action do in Cloudflare?

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.

What inputs does List DNS Records 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 List DNS Records support batch operations?

Run List DNS Records 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