BusyBot
Search all guides

Reference · Credentials

Connect HTTP Bearer to BusyBot

Used by 1 BusyBot node.

Type httpBearerToken 1 field

Fields

FieldTypeRequiredNotes
Token
token		 password Yes Bearer token value (without "Bearer " prefix)

Setting up HTTP Bearer Token

  1. 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.
  2. In BusyBot, open Credentials → Add credential and choose HTTP Bearer Token.
  3. Paste each value into the matching field and save.
  4. 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, 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 HTTP Bearer credentials?

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

What does a HTTP Bearer credential need?

One field: Token. Required: Token. The values come from your own HTTP Bearer account.

How are HTTP Bearer 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 HTTP Bearer Token

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