BusyBot
Search all guides

Reference · Credentials

Connect HighLevel to BusyBot

Used by 1 BusyBot node.

Type highLevelOAuth2 6 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes —
Refresh Token
refreshToken		 password Yes —
Client ID
clientId		 string Yes —
Client Secret
clientSecret		 password Yes —
Location ID
locationId		 string Yes HighLevel location/sub-account ID.
Token Expiry (Unix timestamp)
expiresAt		 string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up HighLevel OAuth2

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

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

What does a HighLevel credential need?

6 fields: Access Token, Refresh Token, Client ID, Client Secret, Location ID, Token Expiry (Unix timestamp). Required: Access Token, Refresh Token, Client ID, Client Secret, Location ID. The values come from your own HighLevel account.

How are HighLevel 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.

Does HighLevel use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret, Location ID, Token Expiry (Unix timestamp)): you approve access in HighLevel, and the resulting tokens are stored encrypted like every other credential.

Nodes that use HighLevel OAuth2

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