ActionCloudflareUpdated June 2026

How do I create a Cloudflare DNS record?

Short answer: Drop the "CloudflareCreate DNS Record" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Zone ID
zone_id
stringRequiredZone ID. Example: 023e105f4ecef8ad9ca31a8372d0c353
Record Type
type
optionsRequiredRecord Type. Options: A, AAAA, CNAME, MX, TXT, NS, SRV
Name
name
stringRequiredDNS record name (e.g. @ for root, www for subdomain)
Content
content
stringRequiredRecord value (IP address, hostname, or text)
TTL
ttl
stringOptionalTime to live in seconds. Use 1 for automatic.
Proxied (orange cloud)
proxied
optionsOptionalProxied (orange cloud). Options: Yes, No (DNS only)
Sample request
{
"zone_id": "e.g. 023e105f4ecef8ad9ca31a8372d0c353",
"type": "{{trigger.type}}",
"name": "e.g. www",
"content": "e.g. 192.0.2.1",
"ttl": "1"
}
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 Create DNS Record.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create DNS Record.

What does the Create DNS Record action do in Cloudflare?
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.
What inputs does Create DNS Record require?
Required: Zone 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 Create DNS Record support batch operations?
Yes. Run Create 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

Other Cloudflare actions.

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

Send create dns record from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.