Can MQTT connect with Spotify?

Yes, MQTT can connect with Spotify using n8n.io. With n8n, you can create workflows that automate tasks and transfer data between MQTT and Spotify. Configure nodes for MQTT and Spotify in the n8n interface, specifying actions and triggers to set up their connection.

Can I use MQTT’s API with n8n?

Yes, with n8n, you can programmatically interact with MQTT’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Can I use Spotify’s API with n8n?

Yes, with n8n, you can programmatically interact with Spotify’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Is n8n secure for integrating MQTT and Spotify?

Yes, it is safe to use n8n to integrate MQTT and Spotify. n8n offers various features to ensure the safe handling of your data. These include encrypted data transfers, secure credential storage, RBAC functionality, and compliance with industry-standard security practices (SOC2 compliant). For hosted plans, data is stored within the EU on servers located in Frankfurt, Germany. You can also host it on your own infrastructure for added control. Learn more about n8n’s security practices here.

How to get started with MQTT and Spotify integration in n8n.io?

To start integrating MQTT and Spotify in n8n, you have different options depending on how you intend to use it: n8n Cloud: hosted solution, no need to install anything. Self-host: recommended method for full-control or customized use cases. Unlike other platforms that charge per operation, step, or task, n8n charges only for full workflow executions. This approach guarantees predictable costs and scalability, no matter the complexity or volume of your workflows.

Back to Integrations

MQTT

Spotify

MQTT and Spotify integration

Save yourself the work of writing custom integrations for MQTT and Spotify and use n8n instead. Build adaptable and scalable Development, Communication, and Miscellaneous workflows that work with your technology stack. All within a building experience you will love.

Get started

See n8n in action

How to connect MQTT and Spotify

Step 1: Create a new workflow
Step 2: Add and configure nodes
Step 3: Connect
Step 4: Customize and extend your integration
Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

MQTT and Spotify integration: Create a new workflow and add the first step

Step 2: Add and configure MQTT and Spotify nodes

You can find MQTT and Spotify in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure MQTT and Spotify nodes one by one: input data on the left, parameters in the middle, and output data on the right.

MQTT and Spotify integration: Add and configure MQTT and Spotify nodes

Step 3: Connect MQTT and Spotify

A connection establishes a link between MQTT and Spotify (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

MQTT and Spotify integration: Connect MQTT and Spotify

Step 4: Customize and extend your MQTT and Spotify integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect MQTT and Spotify with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

MQTT and Spotify integration: Customize and extend your MQTT and Spotify integration

Step 5: Test and activate your MQTT and Spotify workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from MQTT to Spotify or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

MQTT and Spotify integration: Test and activate your MQTT and Spotify workflow

IOT Button Remote / Spotify Control Integration with MQTT

Setup
Create an MQTT Credential item in n8n and assign it to the MQTT Trigger node
Modify the MQTT trigger node to match the topic for your IOT device messages
Modify the switch/router nodes to map to the message text from your IOT button (e.g. arrow_left_click, brightness_up_click, etc.)
Create a Spotify developer-account (or use the login for a user-account)
Create an "App" in the developer-account to represent the n8n workflow
Chicken/Egg ALERT: The n8n Spotify Credentials dialog box will display the "OAuth Redirect URL" required to create the App in Spotify, but the n8n Credential item itself cannot be created until AFTER the App has been created.
Create a Spotify Credentials item in n8n
Open the Settings on the Spotify App to find the required Client ID and Client Secret information.
ALERT: Save this before proceeding to the Connect step.
Connect the n8n Spotify Credential item to the Spotify user-account
ALERT: Expect n8n to open a separate OAuth2 window on authorization.spotify.com here, which may require a login to the Spotify user-account
Open each of the HTTP and Spotify nodes, one by one, and re-assign to your Spotify Credential (try not to miss any).
(Then, probably, upvote this feature request: https://community.n8n.io/t/select-credentials-via-expression/5150
Modify the variable values in the Globals node to match your own environment.
target_spotify_playback_device_name - The name of a playback device available to the Spotify user-account
favorite_playlist_name - The name of a playlist to start when one of the button actions is indicated in the MQTT message. Used in example "Custom Function 2" sequence.

Notes
You're on your own for getting the multi-button remote switch talking to MQTT, figuring out what the exact MQTT topic name is, and mapping the message parts to the workflow (actions, etc.).
The next / previous actions are wired up to not transfer control to the target device. This alternative routing just illustrates a different behavior than the remaining actions/functions, which include activation of the target device when required.
Some of the Spotify API interactions use the Spotify node in n8n, but many of the available Spotify API functions are limited or not implemented at all in the Spotify node. So, in other cases, a regular HTTP node is used with the Spotify OAuth2 API credential instead. By modifying one of the examples included in the template, it should be possible to call nearly anything the Spotify API has to offer.

Spotify+n8n OAuth Mini-Tutorial
Definitions
The developer-account is the Spotify login for creating a spotify-app which will be associated with a client id and client secret.
The user-account is the Spotify login that has permission to stream songs, set up playback devices, etc.
++A spotify-login allows access to a Spotify user-account, or a Spotify developer-account, OR BOTH++
The spotify-app, which has a client id and client secret, is an object created in the developer-account.
The app-implementation (in this case, an ++n8n workflow++) uses the spotify-app's credentials (client id / client secret) to call Spotify API endpoints on behalf of a user-account.

Using One Spotify Login as Both User and Developer
When an n8n Spotify-node or HTTP-node (i.e. an app-implementation) calls a Spotify API endpoint, the Credentials item may be using the client id and client secret from a spotify-app, which was created in a developer-account that is ++one and the same spotify-login as the user-account++. However, it helps to remind yourself that from the Spotify API server's perspective, the developer-account + spotify-app, and the user-account, are ++two independent entities++.

n8n Spotify-OAuth2-API Credential Authorization Process
The 2 layers/steps, in the process of authorizing an n8n Spotify-OAuth2-API credential to make API calls, are:
n8n must identify itself to Spotify as the app-implementation associated with the developer-account/spotify-app by sending the app's credentials (client id and client secret) to Spotify.
The Client ID and Client Secret are supplied in the n8n Spotify OAuth2 Credentials UI/dialog-box
Separately, n8n must obtain an authorization token from Spotify to represent the permissions granted by the user to execute actions (call API endpoints) on behalf of the user (i.e. access things that belong to the user-account).
This authorization for the user-account access is obtained when the "Connect" or "Reconnect" button is clicked in the n8n Spotify Credentials UI/dialog-box (which pops up a separate authorization UI/browser-window managed by Spotify).
The Authorization for a given spotify-app stays "registered" in the user-account until revoked.
See: https://support.spotify.com/us/article/spotify-on-other-apps/
Direct Link: https://www.spotify.com/account/apps/
More than one user-account can be authorized for a given spotify-app. A particular n8n Spotify-OAuth2-API credential item appears to cache an authorization token for the user-account that was most recently authorized.
Up to 25 users can be allowed access to a spotify-app in Developer-Mode, but any user-account other than the one associated with the developer-account must be added by email address at https://developer.spotify.com/dashboard/{{app-credential-id}}/users
ALERT: IF the browser running the n8n UI is ALSO logged into a Spotify account, and the spotify-app is already authorized for that Spotify account, the "reconnect" button in the Spotify-OAuth2-API credential dialog may automatically grab a token for that logged in user-account, offering no opportunity to select a different user-account.
This can be managed somewhat by using "incognito" browser windows for n8n, Spotify, or both.

References
n8n Spotify Credentials Docs
Spotify Authorization Docs

Nodes used in this workflow

Get started

Copy workflow

Popular MQTT and Spotify workflows

IOT Button Remote / Spotify Control Integration with MQTT

Overview This template integrates an IOT multi-button switch (meant for controlling a dimmable light) with Spotify playback functions, via MQTT messages. This isn't likely to work without some tinkering, but should be a good head start on receiving/routing IOT/MQTT messages and hooking up to a Spotify-like API. Requirements An IOT device capable of generating events that can be delivered as MQTT messages through an MQTT Broker e.g. Ikea Strybar remote An MQTT Broker to which n8n can connect and consume messages e.g. Zigbee2MQTT in HomeAssistant A Spotify developer-account (which provides access to API functions via OAuth2 authorization) A Spotify user-account (which provides access to Spotify streamed content, user settings, etc.) Setup Create an MQTT Credential item in n8n and assign it to the MQTT Trigger node Modify the MQTT trigger node to match the topic for your IOT device messages Modify the switch/router nodes to map to the message text from your IOT button (e.g. arrow_left_click, brightness_up_click, etc.) Create a Spotify developer-account (or use the login for a user-account) Create an "App" in the developer-account to represent the n8n workflow Chicken/Egg ALERT: The n8n Spotify Credentials dialog box will display the "OAuth Redirect URL" required to create the App in Spotify, but the n8n Credential item itself cannot be created until AFTER the App has been created. Create a Spotify Credentials item in n8n Open the Settings on the Spotify App to find the required Client ID and Client Secret information. ALERT: Save this before proceeding to the Connect step. Connect the n8n Spotify Credential item to the Spotify user-account ALERT: Expect n8n to open a separate OAuth2 window on authorization.spotify.com here, which may require a login to the Spotify user-account Open each of the HTTP and Spotify nodes, one by one, and re-assign to your Spotify Credential (try not to miss any). (Then, probably, upvote this feature request: https://community.n8n.io/t/select-credentials-via-expression/5150 Modify the variable values in the Globals node to match your own environment. target_spotify_playback_device_name - The name of a playback device available to the Spotify user-account favorite_playlist_name - The name of a playlist to start when one of the button actions is indicated in the MQTT message. Used in example "Custom Function 2" sequence. Notes You're on your own for getting the multi-button remote switch talking to MQTT, figuring out what the exact MQTT topic name is, and mapping the message parts to the workflow (actions, etc.). The next / previous actions are wired up to not transfer control to the target device. This alternative routing just illustrates a different behavior than the remaining actions/functions, which include activation of the target device when required. Some of the Spotify API interactions use the Spotify node in n8n, but many of the available Spotify API functions are limited or not implemented at all in the Spotify node. So, in other cases, a regular HTTP node is used with the Spotify OAuth2 API credential instead. By modifying one of the examples included in the template, it should be possible to call nearly anything the Spotify API has to offer. Spotify+n8n OAuth Mini-Tutorial Definitions The developer-account is the Spotify login for creating a spotify-app which will be associated with a client id and client secret. The user-account is the Spotify login that has permission to stream songs, set up playback devices, etc. ++A spotify-login allows access to a Spotify user-account, or a Spotify developer-account, OR BOTH++ The spotify-app, which has a client id and client secret, is an object created in the developer-account. The app-implementation (in this case, an ++n8n workflow++) uses the spotify-app's credentials (client id / client secret) to call Spotify API endpoints on behalf of a user-account. Using One Spotify Login as Both User and Developer When an n8n Spotify-node or HTTP-node (i.e. an app-implementation) calls a Spotify API endpoint, the Credentials item may be using the client id and client secret from a spotify-app, which was created in a developer-account that is ++one and the same spotify-login as the user-account++. However, it helps to remind yourself that from the Spotify API server's perspective, the developer-account + spotify-app, and the user-account, are ++two independent entities++. n8n Spotify-OAuth2-API Credential Authorization Process The 2 layers/steps, in the process of authorizing an n8n Spotify-OAuth2-API credential to make API calls, are: n8n must identify itself to Spotify as the app-implementation associated with the developer-account/spotify-app by sending the app's credentials (client id and client secret) to Spotify. The Client ID and Client Secret are supplied in the n8n Spotify OAuth2 Credentials UI/dialog-box Separately, n8n must obtain an authorization token from Spotify to represent the permissions granted by the user to execute actions (call API endpoints) on behalf of the user (i.e. access things that belong to the user-account). This authorization for the user-account access is obtained when the "Connect" or "Reconnect" button is clicked in the n8n Spotify Credentials UI/dialog-box (which pops up a separate authorization UI/browser-window managed by Spotify). The Authorization for a given spotify-app stays "registered" in the user-account until revoked. See: https://support.spotify.com/us/article/spotify-on-other-apps/ Direct Link: https://www.spotify.com/account/apps/ More than one user-account can be authorized for a given spotify-app. A particular n8n Spotify-OAuth2-API credential item appears to cache an authorization token for the user-account that was most recently authorized. Up to 25 users can be allowed access to a spotify-app in Developer-Mode, but any user-account other than the one associated with the developer-account must be added by email address at https://developer.spotify.com/dashboard/{{app-credential-id}}/users ALERT: IF the browser running the n8n UI is ALSO logged into a Spotify account, and the spotify-app is already authorized for that Spotify account, the "reconnect" button in the Spotify-OAuth2-API credential dialog may automatically grab a token for that logged in user-account, offering no opportunity to select a different user-account. This can be managed somewhat by using "incognito" browser windows for n8n, Spotify, or both. References n8n Spotify Credentials Docs Spotify Authorization Docs

Build your own MQTT and Spotify integration

Create custom MQTT and Spotify workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Spotify supported actions

Get

Get an album by URI or ID

Get New Releases

Get a list of new album releases

Get Tracks

Get an album's tracks by URI or ID

Search albums by keyword

Get

Get an artist by URI or ID

Get Albums

Get an artist's albums by URI or ID

Get Related Artists

Get an artist's related artists by URI or ID

Get Top Tracks

Get an artist's top tracks by URI or ID

Search artists by keyword

Get Liked Tracks

Get the user's liked tracks

Get Following Artists

Get your followed artists

Add Song to Queue

Add a song to your queue

Currently Playing

Get your currently playing track

Next Song

Skip to your next track

Pause

Pause your music

Previous Song

Skip to your previous song

Recently Played

Get your recently played tracks

Resume

Resume playback on the current active device

Set Volume

Set volume on the current active device

Start Music

Start playing a playlist, artist, or album

Add an Item

Add tracks to a playlist by track and playlist URI or ID

Create a Playlist

Create a new playlist

Get

Get a playlist by URI or ID

Get the User's Playlists

Get a user's playlists

Get Tracks

Get a playlist's tracks by URI or ID

Remove an Item

Remove tracks from a playlist by track and playlist URI or ID

Search playlists by keyword

Get

Get a track by its URI or ID

Get Audio Features

Get audio features for a track by URI or ID

Search tracks by keyword

MQTT and Spotify integration details

MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). It is intended to link faraway devices with a tiny code footprint and low network traffic by acting as a very lightweight publish/subscribe message transport.

MQTT node docs + examples

MQTT credential docs

See MQTT integrations

Related categories

Development

Communication

Spotify is a digital music service that allows you to listen to millions of songs streaming on different devices. It contains music from any genre and era, including the hits of the moment.

Spotify node docs + examples

Spotify credential docs

See Spotify integrations

Related categories

Miscellaneous

Other integrations with MQTT