Short answer: Drop the "Cloudflare → Create DNS Record" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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) |
{"zone_id": "e.g. 023e105f4ecef8ad9ca31a8372d0c353","type": "{{trigger.type}}","name": "e.g. www","content": "e.g. 192.0.2.1","ttl": "1"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.