Spotify n8n integrationAutomate Spotify with n8n.

Point this at one album and Spotify returns its record: title, release information, cover art and the artists credited on it.

• Album ID: the album's Spotify URI or ID, in the spotify:album:1YZ3k65Mqw3G8FzYlW1mmp form. When the value arrives from an earlier node, an expression like {{ $json.id }} reads it off the incoming item, and n8n blocks the run if the field ends up empty.

Spotify keeps a rolling list of albums that just came out, and this operation reads it without any ID to supply.

• Return All: on, n8n walks the pages of the release feed until it runs out; off, it stops at Limit.
• Limit: how many albums come back when Return All is off.
• Country: optional, under Filters, to read the releases of one country rather than the default feed.

Here the album stays in the background and its track listing comes out, one item per song.

• Album ID: the same URI or ID as the album lookup, often {{ $json.id }} chained from a search.
• Return All: on for a complete listing, which matters on long compilations.
• Limit: the ceiling when Return All is off, so a short result usually means this value, not a missing track.

No identifier to hand? Type words instead and get matching albums back, each with the ID the other operations expect.

• Search Keyword: the term to search for, free text, frequently {{ $json.query }} from a form or a spreadsheet row.
• Return All: on to page through every match, which is rarely what you want on a vague keyword.
• Limit: the number of matches to keep.
• Country: optional, under Filters, restricts results to what is playable in that market.

One artist in, one record out, with the name, genres and images Spotify holds for them.

• Artist ID: the artist's Spotify URI or ID, shaped like spotify:artist:4LLpKhyESsyAXpc4laK94U. The plain ID works too, and the field is required, so an empty expression stops the node.

A discography in one call: every album credited to the artist comes back as a separate item.

• Artist ID: the artist's URI or ID, the same value the artist lookup takes.
• Return All: on, n8n keeps requesting pages until the discography is complete.
• Limit: the cap when Return All is off, handy when only the recent output matters.

Spotify maintains its own list of artists close to a given one, and this operation hands that list to the workflow.

• Artist ID: the URI or ID of the artist you want neighbours for, commonly {{ $json.id }} from an artist search that ran just before.

Popularity is local, so this operation asks which country you mean before returning an artist's most played songs.

• Artist ID: the artist's Spotify URI or ID.
• Country: required here, and it is free text rather than a dropdown. Enter the postal abbreviation, US for instance, and expect a different ranking per market.

Same idea as the album search, pointed at performers, with one quirk worth knowing.

• Artist ID: the node still asks for it and marks it required, so leave a value in place even though the keyword drives the search.
• Search Keyword: the term to look for.
• Return All: on to page through every match.
• Limit: the maximum number of artists returned.
• Country: optional, under Filters, keeps only what is playable in that market.

The Library resource has a single operation, and it reads the songs saved on the authorized account.

• Return All: on for the whole library, which is the only setting that makes sense for a backup.
• Limit: with Return All off, the number of saved tracks to bring back, newest first.

Following an artist is not the same as playing one, and this operation lists everyone the authorized account follows.

• Return All: on, every followed artist comes back page after page.
• Limit: the ceiling when Return All is off.

Rather than interrupting what plays, this operation slots a track behind it in the queue.

• Track ID: a track URI or ID, written like spotify:track:0xE4LEFzSNGsz1F6kvXsHU, often {{ $json.id }} from a track search.

This one takes no fields at all. n8n asks the account what is playing right now and returns the track, with nothing to configure beyond the credential.

The workflow equivalent of pressing skip: playback moves to whatever sits next in the queue, and no parameter is needed.

Silence, in one node and zero fields. Playback stops on the active device and the position is kept, which is what makes the resume operation useful afterwards.

Going backwards works the same way as skipping forward, without any field to fill in.

Listening history, freshest first, is what comes out of this operation.

• Return All: on, n8n pages through the history Spotify keeps.
• Limit: the number of past tracks to return when Return All is off, which is usually enough for a daily run.

Playback picks up on the current active device, from where it stopped, and again there is nothing to configure.

Loudness becomes a workflow variable here, applied to the current active device.

• Volume: the volume percentage to set, a number rather than a step up or down, so the workflow decides the exact level instead of nudging it.

Playback begins from a container rather than a single song: a playlist, an artist or an album, whichever URI you hand over.

• Resource ID: a playlist, artist or album URI or ID, for example spotify:album:1YZ3k65Mqw3G8FzYlW1mmp. One field covers the three types, so the same node can start any of them.

This operation pushes a track into a playlist that already exists on the connected account, so a workflow can fill a playlist track by track instead of someone dragging songs in the app.

• Playlist ID: the playlist's Spotify URI or its ID, in the form spotify:playlist:37i9dQZF1DWUhI3iC1khPH.
• Track ID: the track's Spotify URI or ID, the track to add to the playlist, often {{ $json.id }} from a search step.
• Position: an optional field that sets where the new track lands in the playlist.

Here the node creates a brand new playlist on the connected account and hands back its ID, which every later playlist operation needs as input.

• Name: the name of the playlist to create, such as Favorite Songs. Build it with an expression when the name carries a date or a campaign label.
• Description: optional free text shown under the playlist title.
• Public: optional switch that decides whether the playlist is publicly accessible.

Point the node at one playlist and it returns that playlist's own data, without its track list. Useful when a workflow needs to confirm a playlist still exists before writing to it.

• Playlist ID: the playlist's Spotify URI or its ID. Both forms work, so spotify:playlist:37i9dQZF1DWUhI3iC1khPH and the bare ID behind it lead to the same result.

Rather than one playlist, this operation lists the playlists tied to the connected account, one item per playlist, which gives a workflow something to loop over.

• Return All: turned on, n8n walks through the API pages and brings back every playlist; turned off, it stops at Limit.
• Limit: the maximum number of playlists returned when Return All stays off.

Reading the contents of a playlist happens here: n8n returns the tracks it holds, one n8n item per track, ready for a filter, a loop or an export node.

• Playlist ID: the playlist's Spotify URI or its ID, the playlist to read.
• Return All: on for a full export of a long playlist, since the API sends tracks page by page.
• Limit: caps the number of tracks when Return All is off.

Cleanup is the mirror of Add an Item: the node takes a track out of a playlist and leaves the rest untouched.

• Playlist ID: the playlist's Spotify URI or its ID, the playlist being edited.
• Track ID: the track's Spotify URI or ID, the track to delete from the playlist, such as spotify:track:0xE4LEFzSNGsz1F6kvXsHU.

Keyword search runs across Spotify's public playlists and returns matches as items, which makes it a discovery step rather than an editing one.

• Search Keyword: the keyword term to search for, wired to a form or chat message with {{ $json.query }} when the search comes from a user.
• Return All and Limit: all matches, or a capped list.
• Country: an optional filter; with a country code set, only content playable in that market comes back.

One track in, that track's Spotify data out. This is the operation a workflow calls when it holds an identifier and needs the readable details behind it.

• Track ID: the track's Spotify URI or ID. A URI like spotify:track:0xE4LEFzSNGsz1F6kvXsHU works, and so does the ID alone, which matters when the value arrives from another node as {{ $json.trackId }}.

Spotify computes a set of audio features for each track, and this operation returns them for the track you name. It answers questions about how a track sounds, not about who released it.

• Track ID: the track's Spotify URI or ID, the track whose features get pulled. Chain it after a search step so the identifier comes from the previous node.

Free text goes in, matching tracks come out, each one carrying the identifier the other track and playlist operations expect.

• Search Keyword: the keyword term to search for.
• Track ID: the node still marks the track's Spotify URI or ID as required on this operation, so leave a value in the field.
• Return All and Limit: every match, or a short list to keep executions light.
• Country: optional, restricts results to content playable in that market.