Skip to content
For LLMsView as Markdown·

Cloudflare

Manage DNS records, zones, Workers, and security rules with the Cloudflare API.

DetailValue
CategoryCloud & Infra
Base URLhttps://api.cloudflare.com/client/v4
AuthenticationBearer Token
Endpoints6
Connector keycloudflare

Using Cloudflare in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Cloudflare from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /zonesList zones
GET /zones/{zone_id}/dns_recordsList DNS records
POST /zones/{zone_id}/dns_recordsCreate a DNS record
PUT /zones/{zone_id}/dns_records/{dns_record_id}Update a DNS record
DELETE /zones/{zone_id}/dns_records/{dns_record_id}Delete a DNS record
GET /zones/{zone_id}/analytics/dashboardGet zone analytics

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /zones

List zones

DetailValue
Operation IDcloud.listZones
MethodGET
Path/zones

Parameters

NameLocationTypeRequired
namequerystringNo
per_pagequeryintegerNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.listZones.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.

GET /zones/{zone_id}/dns_records

List DNS records

DetailValue
Operation IDcloud.listDnsRecords
MethodGET
Path/zones/{zone_id}/dns_records

Parameters

NameLocationTypeRequired
zone_idpathstringYes
typequerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.listDnsRecords.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.

POST /zones/{zone_id}/dns_records

Create a DNS record

DetailValue
Operation IDcloud.createDnsRecord
MethodPOST
Path/zones/{zone_id}/dns_records

Parameters

NameLocationTypeRequired
zone_idpathstringYes

Request Body

FieldType
typestring
namestring
contentstring
proxiedboolean

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.createDnsRecord.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.

PUT /zones/{zone_id}/dns_records/{dns_record_id}

Update a DNS record

DetailValue
Operation IDcloud.updateDnsRecord
MethodPUT
Path/zones/{zone_id}/dns_records/{dns_record_id}

Parameters

NameLocationTypeRequired
zone_idpathstringYes
dns_record_idpathstringYes

Request Body

FieldType
typestring
namestring
contentstring

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.updateDnsRecord.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.

DELETE /zones/{zone_id}/dns_records/{dns_record_id}

Delete a DNS record

DetailValue
Operation IDcloud.deleteDnsRecord
MethodDELETE
Path/zones/{zone_id}/dns_records/{dns_record_id}

Parameters

NameLocationTypeRequired
zone_idpathstringYes
dns_record_idpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.deleteDnsRecord.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.

GET /zones/{zone_id}/analytics/dashboard

Get zone analytics

DetailValue
Operation IDcloud.getAnalytics
MethodGET
Path/zones/{zone_id}/analytics/dashboard

Parameters

NameLocationTypeRequired
zone_idpathstringYes
sincequerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cloudflare connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.getAnalytics.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudflare API reference.