BusyBot

Reference · Credentials

Anthropic credentials

Used by 12 BusyBot nodes.

Type anthropic 1 field

The Anthropic credential holds an API key for Claude models and unlocks 12 BusyBot nodes, including chat, extended thinking, structured output and search-grounded answers. Create it once in the Anthropic Console and every Claude node can select it. API access is billed separately from Claude.ai subscriptions.

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Your Anthropic API key

Getting your credentials

  1. Sign in to the Anthropic Console with the account that should be billed.
  2. Open the API keys section of your account settings.
  3. Create a new key and name it for where it will be used — for example busybot.
  4. Copy the key immediately; it is shown only once. If you lose it, create a replacement.
  5. Make sure the account has credit or a payment method, since API usage is billed separately from any Claude.ai plan.

Permissions and scopes

Keys carry the access of the organization they belong to. If your organization supports scoping keys to a workspace, create the key in a workspace dedicated to BusyBot so usage is attributable and the key can be revoked in isolation.

Troubleshooting

  • 401 Unauthorized — the key is wrong, revoked, or has whitespace from copying. Create a fresh key and paste it carefully.
  • Credit or billing error — a Claude.ai subscription does not fund API usage. Add credit to the API organization.
  • Model not found — the model chosen on the node is not available to your organization. Select a different one from the node’s dropdown.
  • Overloaded or 529 — Anthropic is under load. Retry with backoff rather than hammering; keep node concurrency modest.

Frequently asked questions

Does a Claude.ai subscription include API access?

No — API usage is billed separately. An active Claude.ai plan does not provide API credit, so the API organization needs its own billing set up.

Can one key serve all the Claude nodes?

Yes. All 12 nodes declaring the Anthropic credential — chat, thinking, structured output, search results and the rest — share this one credential.

What should I do if the key leaks?

Revoke it in the Anthropic Console immediately and create a replacement, then update the credential in BusyBot. Revocation is effective straight away.

Why am I getting overloaded errors?

That is capacity on Anthropic's side rather than anything wrong with your key. Retry with backoff and keep Max Concurrency low on batch workloads.

Nodes that use Anthropic

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

Last updated . Spotted something wrong? Tell us.