Forms & SurveysReal-timeUpdated May 2026

Spotify

Spotify playback and playlist automation

Spotify on Tiny Command exposes the Spotify Web API surface for user-scoped automation — playback control, playlist manipulation, and "currently playing" telemetry. Four actions, no triggers (Spotify doesn't emit user-state webhooks): Get Currently Playing (the track currently playing on any of the user's active devices), Get Current Playback (richer player state — track, context, device, shuffle/repeat, volume, position), Add to Playlist (append track URIs to a playlist the user owns or has edit access to), Get User Profile (the connected user's display name, follower count, country, premium status). The connection uses Spotify OAuth with user-scoped permissions — pick scopes at connection setup based on what the workflow needs (user-read-currently-playing, user-read-playback-state, playlist-modify-private, etc.). Spotify enforces strict scope-checking so over-requesting permissions is common at first; pin to the minimum needed. User Get profile data depends on the country (Spotify content libraries are region-locked).

Connect Spotify

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Spotify can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Add to Spotify Playlist	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.	3 fields	View →
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.	0 fields	View →
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.	0 fields	View →
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.	0 fields	View →

Recipes

Pre-built Spotify workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Spotify → Slack alerts

AI-triage every Spotify event, ping the right channel only when it matters.

Spotify → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Spotify → Notion database

Turn Spotify into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Spotify once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Spotify field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Spotify integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Spotify to Tiny Command?

Open the Tiny Command workflow builder, drop in a Spotify node, and click Connect. Authorize Spotify once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Spotify triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Spotify today. Use Tiny Command's universal Webhook or Schedule trigger to start Spotify workflows, then run any Spotify action you need.

What Spotify actions can I run from a workflow?

4 Spotify actions are available out of the box, covering forms & surveys operations like "Add to Spotify Playlist". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Spotify integration real-time?

Spotify actions execute synchronously inside your workflow. Tiny Command waits for Spotify's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Spotify with Tiny Command?

No. Every Spotify trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Spotify API endpoint directly.

How much does the Spotify integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Spotify integration itself has no per-app surcharge.