Reference · Credentials
HTTP Bearer Token credentials
Used by 1 BusyBot node.
Type
httpBearerToken 1 field Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Tokentoken | password | Yes | Bearer token value (without "Bearer " prefix) |
Setting up HTTP Bearer Token
- In HTTP Bearer Token, create the credential this connection needs — the Token shown above. These are issued from your own HTTP Bearer Token account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose HTTP Bearer Token.
- Paste each value into the matching field and save.
- Add the HTTP Request 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 and are never shown again after saving.
- 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.
Nodes that use HTTP Bearer Token
One credential works across every node below — create it once and reuse it.