Get Currently Playing: Spotify action

Sample request

{}

Returns

{
  "item": {
    "name": "Song Title",
    "album": {
      "name": "Album"
    },
    "artists": [
      {
        "name": "Artist"
      }
    ],
    "duration_ms": 240000
  },
  "is_playing": true,
  "progress_ms": 120000
}

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

FAQ

Questions about Get Currently Playing.

What does the Get Currently Playing action do in Spotify?

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.

What inputs does Get Currently Playing require?

Get Currently Playing has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Get Currently Playing support batch operations?

Yes. Run Get Currently Playing 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