BusyBot
Search all guides

Reference · Credentials

Connect Bubble to BusyBot

Used by 1 BusyBot node.

Type bubbleApi 5 fields

Fields

FieldTypeRequiredNotes
API Token
apiToken		 password Yes Bubble API token from Settings > API.
App Name
appName		 string Yes Your Bubble app name.
Environment
environment		 options Yes —
Hosting
hosting		 options Yes —
Domain
domain		 string No Custom domain (only for self-hosted).

Setting up Bubble API

  1. In Bubble API, create the credential this connection needs — the values listed in the table above. These are issued from your own Bubble API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Bubble API.
  3. Paste each value into the matching field and save.
  4. Add the Bubble 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 Bubble credentials?

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

What does a Bubble credential need?

5 fields: API Token, App Name, Environment, Hosting, Domain. Required: API Token, App Name, Environment, Hosting. The values come from your own Bubble account.

How are Bubble 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 Bubble API

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