Reference · Credentials
Spotify OAuth2 credentials
Used by 1 BusyBot node.
Type
spotifyOAuth2 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Client IDclientId | string | Yes | Spotify application Client ID. Found at https://developer.spotify.com/dashboard under your app settings. |
Client SecretclientSecret | password | Yes | Spotify application Client Secret. Found at https://developer.spotify.com/dashboard under your app settings. |
Access TokenaccessToken | password | Yes | OAuth2 access token from Spotify. Obtain via the OAuth2 authorization flow. |
Refresh TokenrefreshToken | 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
- 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.
- In BusyBot, open Credentials → Add credential and choose Spotify OAuth2.
- Paste each value into the matching field and save.
- 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 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 Spotify OAuth2
One credential works across every node below — create it once and reuse it.