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

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 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 DNS Records support batch operations?

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