Update DNS Record: 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: 023e105f...
Record ID record_id	string	Required	Record ID. Example: rec123
Record Type type	options	Required	Record Type. Options: A, AAAA, CNAME, MX, TXT
Name name	string	Required	Name. Example: www
Content content	string	Required	Content. Example: 192.0.2.1
Proxied proxied	options	Optional	Proxied. Options: Yes, No

Sample request

{
  "zone_id": "e.g. 023e105f...",
  "record_id": "e.g. rec123",
  "type": "{{trigger.type}}",
  "name": "e.g. www",
  "content": "e.g. 192.0.2.1"
}

Returns

{
  "result": {
    "id": "rec123",
    "name": "www.example.com",
    "type": "A",
    "content": "192.0.2.1"
  },
  "success": true
}

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

FAQ

Questions about Update DNS Record.

What does the Update DNS Record action do in Cloudflare?

Updates a DNS record's content, TTL, or proxied flag. Useful for "service migrated to new IP → update A record" deploy automation or for failover-routing workflows that toggle DNS pointing.

What inputs does Update DNS Record require?

Required: Zone ID, Record ID, Record Type, Name, Content. 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 Update DNS Record support batch operations?

Yes. Run Update DNS Record 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