# Clef (Cloudflare) - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/clef

Language: en

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](/docs/credentials) (`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](/docs/credentials) 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` | - | - |
| `model` | `enum` | `"clef"` | `clef`, `clef-flash`, `clef-omni` |
| `state` | `string` | `"{{ input }}"` | - |
| `questions` | `array` | `[{"id":"result","type":"noul","instructions":"","criteria":""}]` | -; max 64 |
| `questions[].id` | `string` | `"result"` | - |
| `questions[].type` | `enum` | `"noul"` | `noul`, `choice`, `score` |
| `questions[].instructions` | `string` | `""` | - |
| `questions[].criteria` | `string` | `""` | - |
| `accountId` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `accountId`<br>Cloudflare account ID | The 32-character hexadecimal account ID from the Cloudflare dashboard. Accepts a workflow expression. |

## Initial configuration

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

```json
{
  "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](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)