ActionCloudflareUpdated June 2026

How do I update a Cloudflare DNS record?

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

Use this action All 6 Cloudflare actions

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

More actions

Other Cloudflare actions.

Action

Create DNS Record

Creates an A, AAAA, CNAME, TXT, MX, or other DNS record on a Cloudflare zone with optional proxied flag for routing through Cloudflare's edge. For "deploy created new subdomain → auto-create DNS record" infrastructure-as-workflow patterns.

Action

Delete DNS Record

Removes a specific DNS record by ID. Irreversible. For "service decommissioned → clean up the DNS record" workflows or for deploy-rollback automation that removes records added by a failed deploy.

Action

List DNS Records

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.

Action

List Zones

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

Action

Purge Cloudflare Cache

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.

How do I update a Cloudflare DNS record?

The fields this action accepts.

Apps that pair well as the trigger for Update DNS Record.

Questions about Update DNS Record.

Other Cloudflare actions.