Add to Spotify Playlist: Spotify action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Playlist ID playlist_id	string	Required	Playlist ID. Example: 37i9dQZF1DXcBWIGoYBM5M
Track URIs uris	string	Required	Comma-separated Spotify track URIs
Position position	string	Optional	Insert at this position (0-based). Leave empty to append.

Sample request

{
  "playlist_id": "e.g. 37i9dQZF1DXcBWIGoYBM5M",
  "uris": "e.g. spotify:track:abc123, spotify:track:def456",
  "position": "e.g. 0"
}

Returns

{
  "snapshot_id": "abc123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Add to Spotify Playlist.

What does the Add to Spotify Playlist action do in Spotify?

Appends track URIs to a playlist the user owns or has edit access to. For "this morning, add tracks released today by my favourite artists" personal-automation workflows.

What inputs does Add to Spotify Playlist require?

Required: Playlist ID, Track URIs. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Spotify returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add to Spotify Playlist support batch operations?

Yes. Run Add to Spotify Playlist inside a Loop node to process arrays. Tiny Command handles Spotify's rate limits automatically so you don't have to throttle manually.

More actions