Spotify

Access music catalog, manage playlists, and control playback via the Spotify Web API.

Detail	Value
Category	Media
Base URL	https://api.spotify.com/v1
Authentication	OAuth2
Endpoints	6
Connector key	spotify

Using Spotify in a workflow

1. Go to Connections and click New Connection.
2. Pick Spotify from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /me	Get current user profile
GET /me/playlists	Get current user playlists
GET /playlists/{playlist_id}	Get a playlist
GET /search	Search for tracks, artists, albums
GET /tracks/{id}	Get a track
GET /artists/{id}	Get an artist

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /me

Get current user profile

Detail	Value
Operation ID	media.getCurrentUser
Method	GET
Path	/me

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.getCurrentUser.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.

GET /me/playlists

Get current user playlists

Detail	Value
Operation ID	media.listPlaylists
Method	GET
Path	/me/playlists

Parameters

Name	Location	Type	Required
limit	query	integer	No
offset	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.listPlaylists.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.

GET /playlists/{playlist_id}

Get a playlist

Detail	Value
Operation ID	media.getPlaylist
Method	GET
Path	/playlists/{playlist_id}

Parameters

Name	Location	Type	Required
playlist_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.getPlaylist.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.

GET /search

Search for tracks, artists, albums

Detail	Value
Operation ID	media.search
Method	GET
Path	/search

Parameters

Name	Location	Type	Required
q	query	string	Yes
type	query	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.search.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.

GET /tracks/{id}

Get a track

Detail	Value
Operation ID	media.getTrack
Method	GET
Path	/tracks/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.getTrack.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.

GET /artists/{id}

Get an artist

Detail	Value
Operation ID	media.getArtist
Method	GET
Path	/artists/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Spotify connection from the Connection dropdown.
3. In the Operation dropdown, select media.getArtist.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Spotify API reference.