BusyBot
Search all guides

Reference · Credentials

Connect Spotify to BusyBot

Used by 1 BusyBot node.

Type spotifyOAuth2 5 fields

Fields

FieldTypeRequiredNotes
Client ID
clientId		 string Yes Spotify application Client ID. Found at https://developer.spotify.com/dashboard under your app settings.
Client Secret
clientSecret		 password Yes Spotify application Client Secret. Found at https://developer.spotify.com/dashboard under your app settings.
Access Token
accessToken		 password Yes OAuth2 access token from Spotify. Obtain via the OAuth2 authorization flow.
Refresh Token
refreshToken		 password No OAuth2 refresh token for automatic token renewal when access token expires.
Token Expiry (Unix timestamp)
expiresAt		 string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up Spotify OAuth2

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

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

What does a Spotify credential need?

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

How are Spotify 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 Spotify use OAuth?

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

Nodes that use Spotify OAuth2

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