HumationHuman + Automation
Back to Catalog

Convert YouTube videos to MP3 with RapidAPI, Google Drive storage & sheets logging

Evoort SolutionsEvoort Solutions
705 views
2/3/2026
AutomationE-commerceShipStationWooCommerceOrder Fulfillment
Official Page

Automated YouTube to MP3 Conversion and Storage with Google Sheets

This automated workflow allows seamless conversion of YouTube videos to MP3, using the YouTube to MP3 Downloader API. The converted MP3 files are uploaded to Google Drive, and all relevant conversion data like download links and file sizes are logged in Google Sheets. Ideal for content creators and download enthusiasts, it enhances efficiency and accuracy in handling YouTube-to-MP3 conversions.

Node-by-Node Explanation:

  1. On form submission

    • Triggers the workflow when a user submits a YouTube video URL for conversion.

  2. HTTP Request

  3. Google Drive

    • Uploads the converted MP3 file to Google Drive for cloud storage.

  4. Google Sheets (Initial Log)

    • Logs initial details such as URL and status in Google Sheets before the conversion is complete.

  5. Google Sheets (Final Log)

    • After successful conversion, logs the download link, file size, and other relevant data in Google Sheets.

  6. If Condition

    • Filters the process to only proceed if the conversion status is "done."

  7. Wait

    • Pauses the workflow until the conversion process is completed.

  8. Code

    • Converts file size from bytes to megabytes (MB) for easier reference in Google Sheets.

  9. Download MP3

    • Triggers the MP3 file download once the conversion is finished.

Problem Solved:

Converting YouTube videos to MP3 manually is time-consuming and tedious. The process involves multiple steps, such as downloading the video, extracting audio, and organizing the files, which can be a hassle, especially if you need to do it frequently. Additionally, managing and tracking these files and their statuses can be chaotic, leading to disorganization.

This workflow automates the entire process:

  • Conversion automation: No need for third-party apps or websites to handle YouTube-to-MP3 conversion.
  • Efficient tracking: All conversion details (file size, download link, etc.) are logged in Google Sheets, keeping everything organized.
  • Cloud storage: Directly stores converted MP3s in Google Drive, ensuring files are secure, easy to access, and well-managed.

By leveraging the YouTube to MP3 Downloader API, this workflow removes all the manual steps, allowing you to save time and effort while keeping everything organized.

Benefits of the Flow:

  • Time-Saving Automation: Automatically converts YouTube videos to MP3 using the YouTube to MP3 Downloader API, eliminating the need for manual conversion.
  • Data Logging: Automatically logs essential conversion details (like file size, download link, etc.) in Google Sheets for easy reference.
  • Cloud Storage Integration: Converted MP3 files are directly uploaded to Google Drive for secure, cloud-based storage.
  • No Hassle: Eliminates the need for third-party tools or manual tracking of conversions.

Use Cases:

  1. Content Creators
    If you’re a YouTuber or a podcast creator, you might need to convert and store multiple audio files for your content. This workflow can help by automatically converting YouTube videos or podcasts to MP3 and saving them to Google Drive, all while keeping a detailed log in Google Sheets.

  2. Educators and Trainers
    Teachers or trainers often use YouTube videos for educational purposes and might want to extract the audio (e.g., for podcasts or lectures). With this automation, they can easily convert YouTube content into MP3 format for use in offline teaching or sharing with students.

  3. Social Media Managers
    Social media managers working with audio content can use this workflow to quickly convert YouTube videos to MP3 files and upload them to Google Drive for easy sharing with their team or posting on social platforms.

  4. Music Enthusiasts
    Music lovers who want to save YouTube music videos or tracks into MP3 format for personal use or offline listening can benefit from this automated conversion process. The workflow makes it fast and easy to convert, store, and track MP3 files.

  5. Content Archivists
    If you’re working on archiving online media or curating content libraries, this system allows for quick and efficient conversion, storing, and cataloging of YouTube videos in MP3 format with all relevant metadata stored in Google Sheets for easy management.

Create your free n8n account and set up the workflow in just a few minutes using the link below:

👉 Start Automating with n8n

Save time, stay consistent, and grow your LinkedIn presence effortlessly!

Convert YouTube Videos to MP3 with RapidAPI, Google Drive Storage & Google Sheets Logging

This n8n workflow automates the process of converting YouTube videos to MP3 audio files, storing them in Google Drive, and logging the conversion details in Google Sheets. It's triggered by a form submission, making it easy to request conversions.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits a form, likely containing the YouTube video URL and potentially other details.
  2. Converts YouTube Video to MP3: It uses an HTTP Request node to interact with a RapidAPI endpoint (or similar service) to convert the provided YouTube video URL into an MP3 audio file.
  3. Waits for Conversion: A "Wait" node is included to pause the workflow, allowing sufficient time for the video conversion service to process the request and generate the MP3.
  4. Checks Conversion Status: An "If" node likely checks the status of the conversion.
    • If Successful:
      • Uploads MP3 to Google Drive: The converted MP3 file is uploaded to a specified folder in Google Drive.
      • Logs to Google Sheets: Details of the successful conversion (e.g., YouTube URL, MP3 file link, timestamp) are recorded in a Google Sheet.
    • If Failed:
      • Logs Error to Google Sheets: Details of the failed conversion are logged in Google Sheets, potentially including an error message.
  5. Executes Custom Code (Optional/Utility): A "Code" node might be used for data manipulation, formatting, or additional logic before or after the API calls or data storage.
  6. Sticky Notes for Documentation: The workflow includes sticky notes for internal documentation or explanations of specific steps.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • RapidAPI Account & API Key: An account with RapidAPI and an API key for a YouTube to MP3 converter service (e.g., "YouTube to MP3 Converter" or similar).
  • Google Account: A Google account with access to:
    • Google Drive: To store the converted MP3 files.
    • Google Sheets: To log the conversion details.
  • n8n Form Trigger: The workflow is initiated by an n8n Form Trigger, which you will need to configure and share.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • RapidAPI: Set up an HTTP Request credential for RapidAPI, including your API key.
    • Google Sheets & Google Drive: Configure Google OAuth2 credentials for both Google Sheets and Google Drive, granting the necessary permissions to read/write sheets and upload files.
  3. Configure the "On form submission" Trigger:
    • Define the fields for your form (e.g., youtubeUrl).
    • Share the form URL to collect submissions.
  4. Configure the "HTTP Request" Node:
    • Update the URL to your chosen YouTube to MP3 RapidAPI endpoint.
    • Map the YouTube URL from the "On form submission" trigger to the API request body/parameters.
    • Ensure headers for RapidAPI key are correctly set.
  5. Configure the "Wait" Node: Adjust the wait time as needed based on the expected conversion duration of the RapidAPI service.
  6. Configure the "If" Node: Set up conditions to check the response from the HTTP Request node to determine if the conversion was successful (e.g., checking for a specific status code or success message).
  7. Configure "Google Drive" Node:
    • Specify the folder ID in Google Drive where the MP3 files should be uploaded.
    • Map the file data (MP3) from the HTTP Request node's output.
    • Define a dynamic filename for the MP3 (e.g., using the YouTube video title).
  8. Configure "Google Sheets" Node:
    • Specify the Spreadsheet ID and Sheet Name for logging.
    • Map the data to be logged (e.g., YouTube URL, MP3 Drive Link, conversion status, timestamp) to the appropriate columns.
  9. Activate the Workflow: Once configured, activate the workflow. Each form submission will now trigger the conversion, storage, and logging process.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942