Cloudflare Tools

Overview

Cloudflare tools let you automate domain and DNS management directly from Zelaxy workflows. Use them to list or inspect zones, create and update DNS records programmatically, and purge cached content — for example, as part of a deployment pipeline that sets a new CNAME and then clears the CDN cache.

Operations

Configuration

cloudflare_list_zones

cloudflare_get_zone

cloudflare_list_dns_records

cloudflare_create_dns_record

cloudflare_update_dns_record

cloudflare_delete_dns_record

cloudflare_purge_cache

At least one of purge_everything, files, tags, hosts, or prefixes must be provided.

Outputs

cloudflare_list_zones

• zones (array) — List of zone objects returned by the Cloudflare API, each containing the full zone metadata (id, name, status, account, nameservers, etc.).
• total_count (number) — Total number of zones matching the filters across all pages.

cloudflare_get_zone

• id (string) — The zone's unique identifier.
• name (string) — The domain name for the zone.
• status (string) — The current zone status (active, pending, initializing, moved).

cloudflare_list_dns_records

• records (array) — List of DNS record objects, each containing id, type, name, content, proxied, ttl, and other metadata.
• total_count (number) — Total number of records matching the filters across all pages.

cloudflare_create_dns_record

• id (string) — The newly created DNS record's unique ID.
• name (string) — The DNS record name.
• type (string) — The DNS record type.

cloudflare_update_dns_record

• id (string) — The updated DNS record's unique ID.
• name (string) — The DNS record name after the update.

cloudflare_delete_dns_record

• id (string) — The ID of the record that was deleted.

cloudflare_purge_cache

• id (string) — A purge-request identifier returned by Cloudflare confirming the operation was queued.

YAML Example

cloudflare_1:
  type: cloudflare
  name: "Cloudflare"
  inputs:
    operation: "cloudflare_create_dns_record"
    apiKey: "{{CLOUDFLARE_API_TOKEN}}"
    zoneId: "{{vars.zoneId}}"
    type: "CNAME"
    name: "app"
    content: "{{deploy.hostname}}"
    proxied: true
    ttl: 1
  connections:
    outgoing:
      - target: purge-cache-block

Tips

• API Token vs Global API Key: Always use a scoped API Token (created in the Cloudflare dashboard under Profile > API Tokens) rather than your Global API Key. Scope it to the minimum permissions needed — for DNS management, grant Zone:DNS:Edit on the relevant zones.
• Chaining zone lookup with DNS operations: If you don't know a Zone ID ahead of time, use cloudflare_list_zones first with a name filter to look it up, then pass {{cloudflare_1.zones[0].id}} into the next block's zoneId input.
• Cache purge scope: purge_everything is the simplest option but invalidates your entire CDN cache. For production sites, prefer targeting specific files or prefixes to avoid a cache-warming spike. Tag-based and host-based purging require an Enterprise plan.