Provider guides
Cloudflare Domains: configuration and operations
Connect the Domain module to Cloudflare Registrar and DNS as separate roles.
On this page
Provider workflow
Connect the Domain module to Cloudflare Registrar and DNS as separate roles. The extension registers cloudflare-registrar for availability and registration, and cloudflare-dns for zone and record management. Renewal is not supported by the registrar adapter, even though Cloudflare itself has domain-renewal features.
Requirements
Agovena Core ^0.0.1. Enable Domain before this extension.
This extension is not marked production-ready. Validate its supported workflow in your own test environment before accepting customer orders.
Set up the package
Enable the Domain module and configure account_id and secret api_token. The manifest makes both fields optional, but actual API operations require nonempty values. Use registrar_key: cloudflare-registrar and, when required, dns_provider_key: cloudflare-dns on the product capability. Confirm your account has access to the Registrar API used by this adapter.
Provider-specific boundaries
The extension uses bearer-token authentication against https://api.cloudflare.com/client/v4. Registrar operations append /accounts/{account_id}/registrar/domain-check or /registrar/registrations. DNS zone discovery is filtered by account and domain. Configure a token whose permissions match the intended role rather than assuming DNS access also grants Registrar access.
For DNS, prepare the zone first, then test an A or TXT record on a domain you control. The adapter accepts type, name, content, ttl and proxied; an id selects update rather than create. TTL must be 1 or between 60 and 86400. Supported type names include A, AAAA, CNAME, MX, NS, SRV, TXT and CAA, but the payload is deliberately small. Do not assume all specialized record fields are implemented. Keep renewal outside this adapter and confirm it directly with the registrar. A created DNS zone is not proof of domain ownership, registration or nameserver propagation. 2
Configuration contract
| Field | Type | Required | Secret | Default |
|---|---|---|---|---|
account_id |
string |
No | No | Empty |
api_token |
string |
No | Yes | Empty |
These are the declared manifest fields. A field marked optional may still be required by an API operation, as described above. Store secret values only in protected settings, never in product descriptions, URLs or shared examples. 1
Operation and failure handling
Registrar requests use account-scoped domain-check and registration endpoints. A missing domain in the availability response is treated as unavailable. Renewal throws an unsupported-operation error. DNS changes require a prepared zone reference and validated record values. The DNS record list requests one page of 100 records, so do not treat it as a complete inventory of a larger zone.