Back to Catalog

Automated 🤖🎵 AI music generation with ElevenLabs, Google Sheets & Drive

DavideDavide
734 views
2/3/2026
Official Page

🤖🎵 This workflow automates the creation, storage, and cataloging of AI-generated music using the Eleven Music API, Google Sheets, and Google Drive.


Key Advantages

Fully Automated Music Generation Pipeline

Once started, the workflow automatically:

  • Reads track parameters
  • Generates music via API
  • Uploads the file
  • Updates your spreadsheet No manual steps needed after initialization.

Centralized Track Management

A single Google Sheet acts as your project control center, letting you organize:

  • Prompts
  • Durations
  • Generated URLs This avoids losing track of files and creates a ready-to-share catalog.

Seamless Integration with Google Services

The workflow:

  • Reads instructions from Google Sheets
  • Saves the MP3 to Google Drive
  • Updates the same Sheet with the final link This ensures everything stays synchronized and easy to access.

Scalable and Reliable Processing

The loop-with-delay mechanism:

  • Processes tracks sequentially
  • Prevents API overload
  • Ensures stable execution This is especially helpful when generating multiple long tracks.

Easy Customization

Because the prompts and durations come from Google Sheets:

  • You can edit prompts at any time
  • You can add more tracks without modifying the workflow
  • You can clone the Sheet for different projects

Ideal for Creators and Businesses

This workflow is perfect for:

  • Content creators generating background music
  • Agencies designing custom soundtracks
  • Businesses needing AI-generated audio assets
  • Automated production pipelines

How It Works

The process operates as follows:

  • The workflow starts manually via the "Execute workflow" trigger
  • It retrieves a list of music track requests from a Google Sheets spreadsheet containing track titles, text prompts, and duration specifications
  • The system processes each track request individually through a batch loop
  • For each track, it sends the text prompt and duration to ElevenLabs Music API to generate studio-quality music
  • The generated MP3 file (in 44100 Hz, 128 kbps format) is automatically uploaded to a designated Google Drive folder
  • Once uploaded, the workflow updates the original Google Sheets with the direct URL to the generated music file
  • A 1-minute wait period between each track generation prevents API rate limiting
  • The process continues until all track requests in the spreadsheet have been processed

Set Up Steps

Prerequisites:

  • ElevenLabs paid account with Music API access enabled
  • Google Sheets spreadsheet with specific columns: TITLE, PROMPT, DURATION (ms), URL
  • Google Drive folder for storing generated music files

Configuration Steps:

  1. ElevenLabs API Setup:

    • Enable Music Generation access in your ElevenLabs account
    • Generate an API key from the ElevenLabs developer dashboard
    • Configure HTTP Header authentication in n8n with name "xi-api-key" and your API value
  2. Google Sheets Preparation:

    • Create or clone the music tracking spreadsheet with required columns
    • Fill in track titles, detailed text prompts, and durations in milliseconds (10,000-300,000 ms)
    • Configure Google Sheets OAuth credentials in n8n
    • Update the document ID in the Google Sheets nodes
  3. Google Drive Configuration:

    • Create a dedicated folder for music uploads
    • Set up Google Drive OAuth credentials in n8n
    • Update the folder ID in the upload node
  4. Workflow Activation:

    • Ensure all API credentials are properly configured
    • Test with a single track entry in the spreadsheet
    • Verify music generation, upload, and spreadsheet update work correctly
    • Execute the workflow to process all pending track requests

The workflow automatically names files with timestamp prefixes (song_yyyyMMdd) and handles the complete lifecycle from prompt to downloadable music file.


Need help customizing?

Contact me for consulting and support or add me on Linkedin.

Automated AI Music Generation with ElevenLabs, Google Sheets, and Google Drive

This n8n workflow automates the process of generating AI music based on text prompts from a Google Sheet, storing the generated audio in Google Drive. It allows for bulk processing of music generation requests.

What it does

This workflow streamlines the creation of AI-generated music by:

  1. Triggering Manually: Initiates the workflow upon a manual trigger, allowing you to control when music generation begins.
  2. Reading Prompts from Google Sheets: Fetches text prompts for music generation from a specified Google Sheet.
  3. Batch Processing: Splits the retrieved prompts into batches to manage API requests efficiently and prevent rate limiting.
  4. Generating Music via ElevenLabs API: For each prompt, it sends a request to the ElevenLabs API to generate an audio file.
  5. Waiting for API Response: Includes a Wait step to handle potential delays or asynchronous processing from the ElevenLabs API.
  6. Storing Audio in Google Drive: Uploads the generated audio files to a designated folder in Google Drive.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: To store your music generation prompts.
  • Google Drive Account: To store the generated audio files.
  • ElevenLabs API Key: An API key for ElevenLabs to access their music generation service.
  • Google OAuth2 Credentials: Configured in n8n for both Google Sheets and Google Drive.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" in the workflows section.
    • Click the three dots next to the workflow name and select "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure Credentials:
    • Google Sheets Node:
      • Click on the "Google Sheets" node (ID: 18).
      • Select or create new Google OAuth2 credentials. Ensure these credentials have access to the Google Sheet you intend to use.
      • Specify the Spreadsheet ID and Sheet Name where your music prompts are located.
    • HTTP Request Node:
      • Click on the "HTTP Request" node (ID: 19).
      • Configure the HTTP Request to interact with the ElevenLabs API. You will likely need to set:
        • Method: POST
        • URL: The specific ElevenLabs API endpoint for music generation.
        • Headers: Include your ElevenLabs API Key (e.g., xi-api-key: YOUR_ELEVENLABS_API_KEY).
        • Body: Construct the JSON body with the text prompt from the Google Sheet (e.g., {"text": "{{ $json.prompt }}"}).
    • Google Drive Node:
      • Click on the "Google Drive" node (ID: 58).
      • Select or create new Google OAuth2 credentials. Ensure these credentials have access to your Google Drive.
      • Specify the Folder ID in Google Drive where you want to save the generated audio files.
      • Configure the File Name and Binary Data fields to use the output from the ElevenLabs API call (e.g., {{ $json.fileName }} and {{ $json.binaryData }}, adjusting based on the actual ElevenLabs response structure).
  3. Prepare your Google Sheet:
    • Create a Google Sheet with a column for your music prompts (e.g., named "Prompt").
    • Populate this column with the text descriptions for the music you want to generate.
  4. Activate and Execute:
    • Ensure all nodes are correctly configured.
    • Click "Activate" to enable the workflow.
    • Click "Execute Workflow" on the "Manual Trigger" node to run the workflow and start generating music.

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