ActionCloudflareUpdated September 2026
How do I create a Cloudflare DNS record?
Short answer: You can create dns record in Cloudflare by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cloudflare Create 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.
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 | Required | Record Type. Options: A, AAAA, CNAME, MX, TXT, NS, SRV |
Name name | string | Required | DNS record name (e.g. @ for root, www for subdomain) |
Content content | string | Required | Record value (IP address, hostname, or text) |
TTL ttl | string | Optional | Time to live in seconds. Use 1 for automatic. |
Proxied (orange cloud) proxied | options | Optional | Proxied (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 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 Create DNS Record support batch operations?
Run Create DNS Record 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
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.
ActionList 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.
ActionList 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").
ActionPurge 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.
ActionUpdate 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.