BusyBot
Search all guides

Reference · Credentials

Connect Cloudflare to BusyBot

Used by 1 BusyBot node.

Type cloudflareApi 2 fields

Fields

FieldTypeRequiredNotes
API Token
apiToken		 password Yes Cloudflare API Token (recommended). Create one at: Cloudflare Dashboard > My Profile > API Tokens.
Email
email		 string No Account email address. Only required when using a Global API Key instead of an API Token.

Setting up Cloudflare API

  1. In Cloudflare API, create the credential this connection needs — the values listed in the table above. These are issued from your own Cloudflare API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Cloudflare API.
  3. Paste each value into the matching field and save.
  4. Add the Cloudflare node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Cloudflare credentials?

One node: Cloudflare. Create the credential once and select it in that node.

What does a Cloudflare credential need?

2 fields: API Token, Email. Required: API Token. The values come from your own Cloudflare account.

How are Cloudflare secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use Cloudflare API

One credential works across every node below — create it once and reuse it.