ActionSpotifyUpdated September 2026

How do I add tracks to a Spotify playlist?

Short answer: You can add to spotify playlist in Spotify by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Spotify Add to Spotify Playlist action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Add to Spotify Playlist in Spotify — start free All 4 Spotify actions

Add to Spotify Playlist in Spotify — start free

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.

Triggered by

Apps that pair well as the trigger for Add to Spotify Playlist.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Spotify

2 Google Sheets triggers

HubSpot → Spotify

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Spotify returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Add to Spotify Playlist support batch operations?

Run Add to Spotify Playlist inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Spotify's rate limits.

More actions

Other Spotify actions.

Action

Get Spotify Current Playback

Returns rich player state — track, context, device, shuffle/repeat, volume, position. For "what am I listening to right now" workflows or for ambient-display integrations.

Action

Get Currently Playing

Returns the track currently playing on any of the user's active devices. Simpler than Get Current Playback when you just need the track identity.

Action

Get Spotify User Profile

Returns the connected user's profile — display name, follower count, country, premium status. Useful for region-aware workflows that need country info.

Add to Spotify Playlist in Spotify — start free