List Saved Tracks

spotify.list_saved_tracks
ActionBusiness appsconnection required

Calls the Spotify API with the connection's credentials.

List the tracks the authorised account has saved to its library.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Spotify
Secret shape
{"client_id": "…", "client_secret": "…", "refresh_token": "…"}
Config it needs
market, device_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
market
ISO 3166-1 alpha-2 country code deciding which catalogue is visible, such as 'US'. Left blank, the connection's default market is used, and the market on the authorised account takes priority over both.
stringNo——US
limit
How many items to return in one page. This endpoint accepts at most 50.
numberNo201–50—
offset
Index of the first item to return, for paging through a large result.
numberNo0≥ 0—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "limit": 20,
  "market": "US",
  "offset": 0
}

Output

One shape.

result

FieldTypeExample
items
The objects on this page, in Spotify's own order.
array—
total
How many items exist across every page.
number—
limit
The page size Spotify actually applied.
number—
offset
The index this page starts at.
number—
next
URL of the next page, or null on the last page.
string—
previous
URL of the previous page, or null on the first page.
string—
{
  "items": [],
  "limit": 0,
  "next": "",
  "offset": 0,
  "previous": "",
  "total": 0
}

See List Saved Tracks run in a workflow.

In a technical demo we add the Spotify connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.