Save or Remove Tracks

spotify.save_tracks

ActionBusiness appsconnection required

Calls the Spotify API with the connection's credentials.

Add tracks to the authorised account's library, or take them out of it.

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

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

Field	Type	Required	Default	Constraints	Example
track_ids Spotify track ids to act on, at most 50 per call. These are bare ids, not URIs.	array	Yes	—	1–50 characters; array of string	["4iV5W9uYEdYUVa79Axb7Rh"]
action Whether to save the tracks to the library or remove them from it.	string	No	save	one of "save", "remove"	—

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

{
  "action": "save",
  "track_ids": [
    "4iV5W9uYEdYUVa79Axb7Rh"
  ]
}

One shape.

Field	Type	Example
ok True when Spotify accepted the change.	boolean	—
action Whether the ids were saved or removed.	string	—
count How many ids were sent.	number	—

{
  "action": "",
  "count": 0,
  "ok": false
}

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.