Structured decisions with Cloudflare Workers AI: choices, scores and yes/no probabilities.
Usage and specifics
Choose a compatible engine and credential, then define the decision schema and input. Structured output must satisfy the contract expected by downstream nodes.
Technical type : clef. 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.
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.
Structured decisions with Cloudflare Workers AI: choices, scores and yes/no probabilities.
Usage and specifics
Choose a compatible engine and credential, then define the decision schema and input. Structured output must satisfy the contract expected by downstream nodes.
Technical type :
clef. Runtime :nodulz.Credentials and prerequisites
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.
credentialIdstringmodelenum"clef"clef,clef-flash,clef-omnistatestring"{{ input }}"questionsarray[{"id":"result","type":"noul","instructions":"","criteria":""}]questions[].idstring"result"questions[].typeenum"noul"noul,choice,scorequestions[].instructionsstring""questions[].criteriastring""accountIdstring""Configuration help
accountIdCloudflare account ID
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "model": "clef", "state": "{{ input }}", "questions": [ { "id": "result", "type": "noul", "instructions": "", "criteria": "" } ], "accountId": "" }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.
See also : Expressions and data, Executions, Node catalog.