Resources · Make integration

Spotify Make integrationAutomate Spotify with Make.

What can Make actually do with your Spotify account? The Spotify Make integration gives you 36 modules: 4 triggers, 20 actions and 12 searches. This page is for curators, podcasters and music marketers who want to wire it up once and walk through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Spotify Make integration let you automate?

The Spotify Make integration links your Spotify account to Make so your library, playlists, followed shows and playback can feed a scenario (the automation you build in Make) or be changed by one. Each step of that scenario is a module: a trigger that starts it, an action that does something, or a search that looks something up.

A playlist that fills itself. Watch Saved Tracks spots each song you like, and Add an Item to a Playlist drops it into a team playlist. Your heart button becomes the curation tool.

A release radar for a label or a blog. Watch Artist's Albums notices when an artist puts out a new album, then Get a Track or List Artist's Top Tracks pulls the details you want to post or log in a spreadsheet app.

A listening log you actually keep. Watch Recently Played Tracks turns each play into a row somewhere else, and Get a Track Audio Features adds the audio profile Spotify holds for that song.

A few honest limits. All 4 triggers are scheduled: Make checks Spotify on the scenario's schedule, it is never pushed by Spotify. You also need a Spotify developer application before the connection works. If you are still weighing platforms, the Make review covers the editor itself, and the same app exists as a node on n8n: see the Spotify n8n integration and the n8n vs Make comparison.

Connect

How do you connect Spotify to Make?

  1. 01

    Register a Spotify developer app

    Open the Spotify Developer Dashboard, click your app's name or Create an App. If Spotify asks for a callback URI, paste https://www.integromat.com/oauth/cb/spotify2. Then copy the Client ID and the Client secret.

  2. 02

    Add a Spotify module in Make

    In your scenario, add any Spotify module and click Create a connection. A connection is your Spotify account linked to Make once, then reused by every Spotify module. The Connection name field is optional.

  3. 03

    Paste the credentials and approve

    Enter the Client ID and Client secret you copied, or follow the on-screen instructions. Once Spotify accepts, the module can read your playlists and library, and every other Spotify module picks the same connection from a dropdown.

First scenario

Your first scenario: liked songs straight into a shared playlist

GoalWhen you save a track in Spotify, Make adds it to a playlist you pick.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Spotify and pick Watch Saved Tracks, the trigger that will start everything.

  2. 02

    Link your account

    Click Create a connection and use the developer app credentials from the section above. From now on, every Spotify module in this scenario reuses that connection.

  3. 03

    Add the playlist action

    Click the + on the right of the trigger and choose Add an Item to a Playlist. Pick the target playlist from the list Make shows you, then map the track coming from the trigger.

  4. 04

    Test with Run once

    Save a song in Spotify, then click Run once. Each module shows the bundles it received (a bundle is one item, here one track). Check the song landed in the playlist.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. New scenarios run every 15 minutes by default, and each module run counts as an operation on your plan. Adjust if needed, then switch the scenario on.

Triggers

What can start a Spotify scenario?

4 modules start a scenario when something happens in Spotify. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Spotify as soon as it happens.

Spotify1Watch Artist's Albums

Watch Artist's Albums

Scheduled trigger

In MakeTriggers when an artist posted a new album.

Keeps an eye on an artist and hands your scenario each new album they put out, so a release never slips past you.

How it fires
scheduled. Make checks Spotify on the scenario's schedule (every 15 minutes by default, the clock badge on the module), so a new album shows up at the next check, not the second it drops.
When to use it
a music blog or label team that wants a draft post or a planning row created each time a tracked artist releases something, picked up at the next check.
Watch out
one album can carry many tracks. If you need them one by one, follow up with a search module.
Spotify2Watch Playlist Tracks

Watch Playlist Tracks

Scheduled trigger

In MakeTriggers when a new track is added to playlist.

Starts your scenario when a song is added to a playlist you choose, which makes a shared playlist behave like an inbox.

How it fires
scheduled. Make polls the playlist on the scenario's schedule and returns every track added since its last look.
When to use it
a collaborative playlist where friends or colleagues suggest songs, and you want each suggestion announced in a chat channel or copied to another playlist.
Watch out
several tracks added between two checks arrive as several bundles, and each one costs operations in the modules that follow.
Spotify3Watch Recently Played Tracks

Watch Recently Played Tracks

Scheduled trigger

In MakeTriggers when a track is played.

Hands your scenario the songs you just listened to. Think of it as the raw material for a listening diary or a play counter.

How it fires
scheduled. Make asks Spotify for recent plays on the scenario's schedule. Nothing is pushed to Make when the song starts.
When to use it
you want every play of your account written to a spreadsheet or a database so you can look back at habits later.
Watch out
a busy listening session produces lots of bundles. Watch your operation count before switching it on.
Spotify4Watch Saved Tracks

Watch Saved Tracks

Scheduled trigger

In MakeTriggers when a new track is saved.

Fires on each song you save to your library, which turns the heart button into a command for Make.

How it fires
scheduled. Make looks at your saved tracks on the scenario's schedule and passes along the new ones.
When to use it
you like a track on your phone and want it added to a team playlist, logged for a DJ set or shared with a group, without opening anything else.
Watch out
during the first Run once test, check which tracks come through before connecting the next module, so you know what counts as new.
Modules

What else can Make do in Spotify?

Spotify gives you 32 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Spotify1

Add an Item to a Playlist

Action

In MakeAdds an item to a playlist.

Drops a track into the playlist you choose. It is the module behind most playlist automations.

When to use it
right after a trigger or a search, when a song should end up in a curated, shared or themed playlist.
Watch out
map the item coming from the previous module, otherwise the same song gets added on every run.
Spotify2

Check a Show

Action

In MakeCheck if the show is already saved in the current user's library.

Answers a yes-or-no question: is this podcast already saved in the account's library? Useful as a guard before doing anything else.

When to use it
before subscribing to a show from a list, so a filter can skip the ones already there.
Spotify3

Create a Playlist

Action

In MakeCreates a new playlist.

Makes a brand new playlist on the connected account, ready to be filled by the next modules.

When to use it
when an event deserves its own playlist, say a new client project, a party or a release campaign that starts in another app.
Watch out
run it once per event, or you will end up with duplicate playlists.
Spotify4

Get a Current Track

Action

In MakeRetrieves the object currently being played on the user’s Spotify account.

Tells you what is playing on the account right now: the track or episode currently on air.

When to use it
a studio or a shop that wants to post the current song on a screen or in a chat channel when someone asks for it.
Watch out
if nothing is playing, there is nothing to return, so plan a filter for that case.
Spotify5

Get an Episode

Action

In MakeRetrieves an existing episode.

Pulls the details of one podcast episode when you already know which one you want.

When to use it
a podcaster who wants the episode's details copied into show notes, a newsletter draft or a content calendar.
Watch out
It needs to know which episode you mean, so place it after a module that hands one over, such as List Episodes.
Spotify6

Get a Player's Status

Action

In MakeRetrieves information about the user’s current playback state, including track or episode, progress, and active device.

Reads the playback state of the account: what is playing, how far along it is and which device is active.

When to use it
before sending a pause or play command, to check there is an active device and something to act on.
Spotify7

Get a Playlist

Action

In MakeRetrieves an existing playlist.

Fetches one playlist and its details, so the next modules can reuse its name or description.

When to use it
when a scenario starts from a playlist link shared in a form or a chat and you need its information before posting it.
Spotify8

Get a Show

Action

In MakeRetrieves an existing show.

Returns the details of one podcast, the show itself rather than a single episode.

When to use it
building a directory of podcasts your team follows, one record per show, in a database app.
Watch out
It covers the show, not its episodes. Add List Episodes after it when you want those too.
Spotify9

Get a Track

Action

In MakeRetrieves an existing track.

Looks up a single song when you already have its reference, and brings back its details for the rest of the scenario.

When to use it
after a trigger that only gives you the basics, to enrich a row or a post with the full track information.
Spotify10

Get a Track Audio Features

Action

In MakeRetrieves audio feature information for a single track.

Returns the audio feature information Spotify holds for one track, a musical profile rather than catalog details.

When to use it
a DJ or a playlist editor who wants to sort songs by their sound before deciding where they go.
Watch out
it works on one track at a time, so each song costs one operation.
Spotify11

Get Items

Action

In MakeRetrieves a collection of objects of described item types.

Retrieves a collection of objects of the item types you describe, in one call, instead of fetching them one by one.

When to use it
you have a handful of references from a spreadsheet and want all their details in a single step.
Watch out
do not mix it up with Search Items. Get Items is an action that fetches what you point to; it does not search.
Spotify12

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends your own request to the Spotify API with the connection you already set up. It covers whatever the other modules do not.

When to use it
a Spotify feature you need has no dedicated module in the list.
Watch out
you write the request yourself, so keep the Spotify API reference open next to you.
Spotify13

Pause a User's Playback

Action

In MakePauses a user's playback.

Stops the music on the connected account, from a scenario instead of a phone.

When to use it
a meeting starts in your calendar app, or a store closes its till, and the music should stop at that moment.
Watch out
pair it with Get a Player's Status if you are not sure something is playing.
Spotify14

Remove a Track

Action

In MakeRemoves an existing track for the current user.

Takes a song out of the current user's saved tracks.

When to use it
cleaning your library when a track was flagged elsewhere, for example in a review sheet where you mark songs to drop.
Watch out
test it with Run once on a song you do not mind losing. Save a Track puts it back if needed.
Spotify15

Save a Track

Action

In MakeSaves a track to the current user’s library.

Adds a song to the account's library, exactly like tapping the heart in the app.

When to use it
a friend sends a track through a form or a message, and you want it saved for later without stopping what you are doing.
Spotify16

Start/Resume a User's Playback

Action

In MakeStarts or resumes a user's playback.

Starts or resumes the music on the account from inside a scenario.

When to use it
opening time in a shop, the end of a meeting, or any event in another app that should bring the music back.
Watch out
List Devices tells you which devices the account can reach, which helps when playback does not start.
Spotify17

Subscribe to a List of Shows

Action

In MakeSubscribes one or more shows to the current user's library.

Follows one or more podcasts in a single step and adds them to the library.

When to use it
someone on the team shares a list of shows to follow, and you want them all added at once.
Watch out
Put Check a Show before it when the list may hold podcasts the account already follows, so you see which ones are really new.
Spotify18

Unsubscribe from a List of Shows

Action

In MakeDeletes one or more shows from the current user's library.

The mirror of the previous module: it removes one or more podcasts from the library.

When to use it
a show ends or a list of podcasts is retired in your tracking sheet, and the library should follow.
Watch out
check the list first with List Shows, since several shows go in one call.
Spotify19

Update a Playlist

Action

In MakeUpdates an existing playlist.

Changes an existing playlist's details so it stays in sync with what happens elsewhere.

When to use it
a campaign moves to a new phase in your project tool, and the playlist should reflect it.
Watch out
Run Get a Playlist first to see what is there now, then change only what needs changing.
Spotify20

Upload a Playlist Cover Image

Action

In MakeUploads a new playlist cover image.

Replaces the artwork of a playlist with a new image.

When to use it
a designer drops the final cover in a shared folder, and the playlist should show it without anyone uploading by hand.
Watch out
on the Free plan, files over 5 MB are out of reach for Make.
Spotify21

List Artist's Albums

Search

In MakeRetrieves a list of artist's albums.

Returns an artist's albums, each one as its own bundle so you can process them in turn.

When to use it
building a discography table for an artist you manage or cover.
Watch out
a long catalog means many bundles and many operations downstream.
Spotify22

List Artist's Top Tracks

Search

In MakeRetrieves artist's top tracks.

Brings back the songs Spotify ranks as an artist's top tracks.

When to use it
a booker preparing a brief, or a scenario that fills a playlist with the best-known songs of a lineup.
Watch out
Each song comes out as its own bundle, so every module after it runs once per track and counts operations.
Spotify23

List Devices

Search

In MakeRetrieves a list of devices.

Shows which devices are available on the account: phone, speaker, computer.

When to use it
before a playback module, to find the right device or to understand why nothing happened.
Watch out
It returns one bundle per device. Add a filter to keep the speaker you want before the playback module.
Spotify24

List Episodes

Search

In MakeRetrieves a list of existing show episodes.

Lists the episodes of a show, one bundle per episode.

When to use it
a podcast team that wants its full back catalog copied into a database to plan reruns or clips.
Watch out
big shows return a lot of episodes. A filter after it keeps only what you need.
Spotify25

List Episodes Information

Search

In MakeRetrieves information about the list of episodes.

Retrieves information about several episodes at once when you already hold their references.

When to use it
a sheet lists episodes picked for a newsletter, and you want their details in one pass.
Watch out
It needs the episode references up front. If you only know the show, start with List Episodes instead.
Spotify26

List Playlists

Search

In MakeRetrieves a list of existing playlists.

Gives you the playlists of the account, each as its own bundle.

When to use it
keeping an inventory of every playlist a brand or a radio team runs, in one table.
Watch out
An account with many playlists sends many bundles. A filter right after keeps only the ones your scenario should touch.
Spotify27

List Playlist's Items

Search

In MakeRetrieves full details of the items of a playlist.

Returns the full details of every item in a playlist, one song or episode per bundle.

When to use it
exporting a playlist to a spreadsheet, or copying it into another one.
Watch out
each item that flows on costs operations in the modules after it.
Spotify28

List Shows

Search

In MakeRetrieves a list of existing shows.

Lists the podcasts saved in the account's library.

When to use it
checking which shows the account follows before a cleanup or a sync with a tracking sheet.
Watch out
It only covers shows saved in the library. To look at one podcast in detail, Get a Show is the better pick.
Spotify29

List Shows Metadata

Search

In MakeRetrieves a list of shows metadata.

Pulls the metadata of several shows in one go, rather than calling Get a Show for each of them.

When to use it
refreshing a podcast directory where you already store the show references.
Watch out
You need the show references first. List Shows can hand them over when the podcasts are already in the library.
Spotify30

List User's Followed Artists

Search

In MakeRetrieves a list of current user’s followed artists.

Returns the artists the account follows, one per bundle.

When to use it
a first step before watching each artist's albums, or a list for a fan newsletter.
Watch out
One bundle per artist means the next modules run once per artist, so filter first if only a few matter to you.
Spotify31

Search Tracks

Search

In MakeSearches for information about tracks that match a keyword string.

Finds songs that match a keyword, the way the Spotify search bar does.

When to use it
a request form gives you a song title and artist, and you need the actual track before adding it to a playlist.
Watch out
a keyword can match several songs. Keep the first result or filter before acting.
Spotify32

Search Items

SearchIn the docs only

A broader search module listed next to Search Tracks. Make shows no official description for it, so open it in the editor to see which item types it covers.

When to use it
when Search Tracks is too narrow for what you are looking up.
Watch out
like any search, it can return zero, one or many bundles.
Need help

Need help automating Spotify with Make?

A person reads every message.

FAQ

Spotify and Make: common questions

01Is the Spotify Make integration free?
Yes. Spotify is a standard app in Make, available from the Free plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your own Spotify subscription is a separate matter, handled on Spotify's side.
02What does it take to connect Spotify to Make?
A Spotify account and a registered developer application. In the Spotify Developer Dashboard, open your app or click Create an App, set the callback URI Make gives in its documentation if Spotify asks, and copy the Client ID and Client secret. Back in Make, add a Spotify module, click Create a connection, paste both values and approve. That single connection then serves all 36 Spotify modules in every scenario you build.
03Do Spotify triggers in Make fire in real time?
No. All 4 Spotify triggers are scheduled and none is instant. Make checks Spotify on the scenario's schedule, every 15 minutes by default, and picks up whatever happened since the last check: new saved tracks, new playlist tracks, recent plays or new albums. On the Free plan, 15 minutes is the shortest interval. On a paid plan you can go down to 1 minute, which gets closer to live without ever being pushed by Spotify.
04What if a Spotify module is missing in Make?
Use Make an API Call. It sends any request to the Spotify API with the connection you already have, so there is nothing new to authorize. It asks for more care than a ready-made module, because you write the request yourself from the Spotify API reference. Before going there, check the 12 search modules and 20 actions: Get Items and Search Items are easy to miss and often cover the case.
05Make or n8n for Spotify: which one fits?
It depends on how you like to work. Make gives you 36 ready modules, a visual editor where each step shows its bundles, and hosting handled for you, which suits someone building their first automations. n8n also has a Spotify node and appeals to teams that want to host the tool themselves or write more code around the flow. Both reach the Spotify API. Pick the one your team will actually maintain.