Spotify Track Conversion to MP3 and Google Drive Sharing - n8n Workflow

Media managers and content creators needing instant file conversion.
Users looking to automate file downloading, conversion, and cloud storage operations.
Technical users who want to leverage external APIs (RapidAPI) within an n8n workflow.
Developers seeking advanced examples of using the n8n trigger for web forms.

This comprehensive n8n workflow template addresses the need for seamless digital media conversion and distribution. Manually converting Spotify links to MP3s and then uploading them is time-consuming. This n8n automation eliminates those steps entirely.

The system utilizes an On form submission n8n trigger to accept the Spotify URL input. It then communicates with a third-party API via an httpRequest n8n node to handle the resource-intensive conversion. To ensure the file is ready, the n8n workflow incorporates a Wait node before downloading the resulting MP3. Finally, the file is securely uploaded to Google Drive using a service account and immediately shared, providing a shareable link back to the user or subsequent systems. This powerful n8n workflow saves significant time and reduces manual effort in file management.

The process begins with the On form submission n8n trigger, which presents a simple form asking the user for the Spotify url. Once submitted, the n8n workflow sends this URL as a multipart-form-data request to the RapidAPI endpoint using the Spotify Rapid Api n8n node for conversion.

The n8n node executes this request and, upon receiving a response (which includes the downloadurl), the n8n workflow proceeds to the Wait node. This pause is crucial to ensure the external API has completed its processing and the MP3 is fully generated and ready for retrieval.

Following the wait, the Downloader n8n node executes a standard HTTP request to fetch the binary MP3 file using the dynamically provided downloadurl. This file is then passed to the Upload Mp3 To Google Drive n8n node, which securely stores it within the configured Google Drive folder.

As the final step in this n8n workflow, the Update Permission n8n node modifies the file's sharing settings, granting public access (to 'anyone'). This means the resulting Google Drive link is instantly shareable, completing the full automation loop initiated by the n8n trigger.

1. Import the n8n Workflow: Copy the provided JSON and import it directly into your n8n instance via the 'New' menu and 'Import from JSON'.


2. Form Trigger Setup: Activate the On form submission n8n trigger node. You will need to copy the generated webhook URL and present it to your users or embed it where necessary.


3. RapidAPI Configuration: Locate the Spotify Rapid Api n8n node. You must replace the placeholder your key in the Header Parameters with your actual RapidAPI Key for the specified service (spotify-downloader-mp3.p.rapidapi.com).


4. Google Drive Credentials: Configure Service Account credentials for Google Drive. Select the Upload Mp3 To Google Drive n8n node and the Update Permission n8n node, and connect them to a valid Google Drive Service Account credential setup in your n8n environment.

On form submission (n8n trigger): The entry point of this n8n workflow. It acts as a webhook and web form, collecting a single parameter named url (the Spotify link).
Spotify Rapid Api (httpRequest n8n node): Sends a POST request to a third-party conversion service. Key configuration includes setting the url parameter dynamically (={{ $json.url }}) and requiring custom HTTP headers for x-rapidapi-host and x-rapidapi-key.
Wait (n8n node): A flow control element that introduces a deliberate delay. This is often necessary in automation processes involving external, asynchronous APIs, ensuring the file is ready before proceeding to the download.
Downloader (httpRequest n8n node): Performs a GET request using the dynamically generated download_url obtained from the previous API call. This node successfully downloads the MP3 file binary data.
Upload Mp3 To Google Drive (googleDrive n8n node): Uploads the binary MP3 file downloaded in the previous step to the designated Google Drive location. It relies on Service Account authentication for background processing.
Update Permission (googleDrive n8n node): Modifies the access control list (ACL) for the newly uploaded file. It sets the role to writer (though reader is often safer for sharing) and the type to anyone, making the file publicly accessible without requiring a Google account login. This finalizes the n8n workflow.