> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.spotify.md).

# Spotify

Use the Spotify node to automate work in Spotify, and integrate Spotify with other applications. n8n has built-in support for a wide range of Spotify features, including getting album and artist information.

On this page, you'll find a list of operations the Spotify node supports and links to more resources.

{% hint style="info" %}
**Credentials**

Refer to [Spotify credentials](/integrations/builtin/credentials/spotify.md) for guidance on setting up authentication.
{% endhint %}

## Operations <a href="#operations" id="operations"></a>

* Album
  * Get an album by URI or ID.
  * Get a list of new album releases.
  * Get an album's tracks by URI or ID.
  * Search albums by keyword.
* Artist
  * Get an artist by URI or ID.
  * Get an artist's albums by URI or ID.
  * Get an artist's related artists by URI or ID.
  * Get an artist's top tracks by URI or ID.
  * Search artists by keyword.
* Library
  * Get the user's liked tracks.
* My Data
  * Get your followed artists.
* Player
  * Add a song to your queue.
  * Get your currently playing track.
  * Skip to your next track.
  * Pause your music.
  * Skip to your previous song.
  * Get your recently played tracks.
  * Resume playback on the current active device.
  * Set volume on the current active device.
  * Start playing a playlist, artist, or album.
* Playlist
  * Add tracks from a playlist by track and playlist URI or ID.
  * Create a new playlist.
  * Get a playlist by URI or ID.
  * Get a playlist's tracks by URI or ID.
  * Get a user's playlists.
  * Remove tracks from a playlist by track and playlist URI or ID.
  * Search playlists by keyword.
* Track
  * Get a track by its URI or ID.
  * Get audio features for a track by URI or ID.
  * Search tracks by keyword

## Templates and examples <a href="#templates-and-examples" id="templates-and-examples"></a>

[Browse Spotify node documentation integration templates](https://n8n.io/integrations/spotify) or [search all templates](https://n8n.io/workflows/)

If this node doesn't support the operation you want to do, you can use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest.md) to call the service's API.

You can use the credential you created for this service in the HTTP Request node:

1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.
2. Select the service you want to connect to.
3. Select your credential.

Refer to [Custom API operations](/integrations/builtin/custom-api-actions-for-existing-nodes.md) for more information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.spotify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.