Duaer

Integrations

Set up Spotify credentials in Duaer

Store Spotify connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Create a Spotify app

The Duaer Spotify OAuth2 API credential:

  1. On the Spotify Developer Dashboard, click Create app, add the Duaer OAuth Redirect URL to Redirect URIs, and tick Web API.
  2. Copy Client ID and Client secret from the app Settings into the credential, then click Connect my account.

In development mode, only Spotify accounts added under User Management can authorize. Spotify requires an HTTPS redirect address, except loopback addresses.

Spotify OAuth2 API fields in Duaer

In Duaer, choose Spotify OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: user-read-playback-state playlist-read-collaborative user-modify-playback-state playlist-modify-public user-read-currently-playing playlist-read-private user-read-recently-played playlist-modify-private user-library-read user-follow-read.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Spotify.

Save the connection in Duaer

Open Credentials and create Spotify. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Spotify secret values appear in Duaer node parameters?

No. In Duaer, Spotify secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Spotify credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Spotify expects, then confirm you can create credentials in that project.

In this section