Cloudflare

Node catalog Actions

On this page

Cloudflare API: DNS, cache, Workers, storage, security and custom requests.

Usage and specifics

Use an API token scoped to the target accounts and zones. Choose resources and operations or configure the trigger monitoring mode, then publish to activate it.

Technical type : cloudflare. Runtime : nodulz.

Credentials and prerequisites

Cloudflare - API (integration / cloudflare). Cloudflare API token scoped to the required permissions. Global keys may use a JSON secret with apiKey and email.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`requestMode`	`enum`	-	`guided`, `advanced`
`operation`	`string`	`"zones-get"`	-
`pathParameters`	`record`	`{}`	-
`queryParams`	`string`	`"{}"`	-
`headers`	`string`	`"{}"`	-
`body`	`string`	`""`	-
`bodyType`	`enum`	`"none"`	`none`, `json`, `text`, `binary`, `multipart`, `form`
`contentType`	`string`	`""`	-
`customMethod`	`enum`	`"GET"`	`GET`, `POST`, `PUT`, `PATCH`, `DELETE`, `HEAD`, `OPTIONS`
`customPath`	`string`	`""`	-
`responseType`	`enum`	`"auto"`	`auto`, `json`, `text`, `binary`

Configuration help

requestMode Parameter input: Guided fields build the request for you. Advanced JSON lets you edit all parameters freely. Switching modes preserves existing values.
customPath API path: Path relative to https://api.cloudflare.com/client/v4 without query parameters or fragment. Example: /zones or /graphql (POST with a JSON body containing query and variables). External URLs and redirects are rejected.
headers Additional headers (JSON): Object of strings, for example for If-Match. Authentication comes from the credential and cannot be replaced here.
bodyType Body format: The suggested format follows the operation. Examples are templates to adapt; check Cloudflare for required fields and limits. GET and HEAD do not accept a body.
contentType Content type: Leave empty for the format default. Example: application/javascript for a Worker script. Multipart manages its header and boundary automatically.
responseType Response format: Automatic follows the Cloudflare Content-Type. JSON preserves the result, result_info, errors and messages envelope; binary returns a base64 Nodulz file.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "operation": "zones-get",
  "pathParameters": {},
  "queryParams": "{}",
  "headers": "{}",
  "body": "",
  "bodyType": "none",
  "contentType": "",
  "customMethod": "GET",
  "customPath": "",
  "responseType": "auto"
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.