Cloudflare - Notification

Node catalog Triggers

On this page

Receive Cloudflare Notifications alerts through an authenticated webhook.

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_trigger. Runtime : nodulz.

Credentials and prerequisites

Cloudflare - Webhook secret (integration / cloudflare_webhook). Shared secret for a Cloudflare Notifications destination, verified through cf-webhook-auth.

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
`rateLimitEnabled`	`boolean`	-	-
`rateLimitMax`	`number`	-	-; > 0
`rateLimitWindowMs`	`number`	-	-; > 0
`allowedIps`	`array`	-	-; max 256
`blockedIps`	`array`	-	-; max 256
`credentialId`	`string`	`""`	-
`alertTypes`	`array`	`[]`	-
`accountId`	`string`	`""`	-
`policyId`	`string`	`""`	-
`testPayload`	`string`	`""`	-

Initial configuration

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

json

{
  "credentialId": "",
  "alertTypes": [],
  "accountId": "",
  "policyId": "",
  "testPayload": ""
}

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.