BusyBot

Reference · Credentials

HighLevel OAuth2 credentials

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 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 HighLevel OAuth2

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