Back to Catalog

Create multi-speaker podcasts with Google Sheets, ElevenLabs v3, and Drive

DavideDavide
917 views
2/3/2026
Official Page

This workflow automates the creation of realistic Multi-speaker podcasts using ElevenLabsv3 API by reading a script from Google Sheets and saving the final MP3 file to Google Drive.

  1. Data Source – Dialogue scripts are stored in a Google Sheet. Each row contains:

    • Speaker name (optional)
    • Voice ID (from ElevenLabs)
    • Text to be spoken
  2. Data Preparation – The workflow transforms the spreadsheet content into the proper JSON format required by the ElevenLabs API.

  3. Podcast Generation – ElevenLabs’ Eleven v3 model converts the prepared text into expressive, natural-sounding dialogue. It supports not only speech but also non-verbal cues and audio effects (e.g., [laughs], [whispers], [clapping]).

  4. File Storage – The generated audio file is automatically uploaded to Google Drive, organized by timestamped filenames.


Key Advantages

  • Seamless Automation – From dialogue writing to final audio upload, everything runs automatically in one workflow.
  • Multi-Speaker Support – Easily assign different voices to multiple characters for dynamic conversations.
  • Expressive & Realistic Output – Supports emotions, speech styles, and ambient effects, making podcasts more immersive.
  • Flexible Content Input – Scripts can be collaboratively written and edited in Google Sheets, with no technical knowledge required.
  • Scalable & Reusable – Can generate multiple podcast episodes in seconds, ideal for content creators, educators, or businesses.
  • Cloud Integration – Final audio files are securely stored in Google Drive, ready to be shared or published.

How It Works

The workflow processes a structured script from a spreadsheet and uses AI to generate a realistic conversation.

  1. Manual Trigger: The workflow is started manually by a user clicking "Execute workflow" in n8n.
  2. Get Dialogue: The "Get dialogue" node fetches the podcast script data from a specified Google Sheet. The sheet should contain columns for Speaker (optional), Voice ID, and the dialogue Input/Text.
  3. Prepare Dialogue: The "Code" node transforms the raw sheet data into the precise JSON format required by the ElevenLabs API. It creates an array of objects where each object contains the text and the corresponding voice_id for each line of dialogue.
  4. Generate Podcast: The "HTTP Request" node sends a POST request to the ElevenLabs Text-to-Dialogue API endpoint (/v1/text-to-dialogue). It sends the transformed dialogue array in the request body, instructing the API to generate a single audio file with a conversation between the specified voices.
  5. Upload File: The "Upload file" node takes the audio file response from ElevenLabs and saves it to a designated folder in Google Drive..

Set Up Steps

To use this workflow, you must complete the following configuration steps:

  1. Prepare the Google Sheet:

    • Clone the Template: Duplicate the [provided Google Sheet template](https://docs.goo# Header 1gle.com/spreadsheets/d/1eB8iUQmhj3xJMpGam_slCS0ivtgTUpbcWAqeutG_HM8/edit?usp=sharing) into your own Google Drive.
    • Fill the Script:
      • Column A (Speaker): Optional. Add speaker names for your reference (e.g., "Host", "Guest").
      • Column B (Voice ID): Mandatory. Enter the unique Voice ID for each line from ElevenLabs.
      • Column C (Input): Mandatory. Write the dialogue text for each speaker. You can use [non-speech audio events] like [laughs] or [whispers] to add expression.
  2. Configure ElevenLabs API Credentials:

    • Login or create FREE account on Elevenlabs
    • Edit the "Generate podcast" node's credentials.
    • Create an HTTP Header Auth credential named "ElevenLabs API".
    • Set the Name to xi-api-key and the Value to your actual ElevenLabs API key.
  3. Configure Google Services:

    • Google Sheets: Ensure the "Get dialogue" node has valid OAuth credentials and that the documentId points to your copy of the script sheet.
    • Google Drive: Ensure the "Upload file" node has valid OAuth credentials and that the folderId points to the correct Google Drive folder where you want the audio files saved.

Need help customizing?

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

Create Multi-Speaker Podcasts with Google Sheets, ElevenLabs (via HTTP Request), and Google Drive

This n8n workflow automates the process of generating multi-speaker podcasts based on content defined in a Google Sheet, using ElevenLabs for text-to-speech, and storing the generated audio files in Google Drive. This streamlines the creation of audio content, making it easier to produce podcasts, audiobooks, or narrated articles with distinct voices for different speakers.

What it does

  1. Triggers Manually: The workflow is initiated manually, allowing you to control when the podcast generation process begins.
  2. Reads Data from Google Sheets: It connects to a specified Google Sheet to read the podcast script, including speaker assignments and corresponding text.
  3. Generates Audio with ElevenLabs (via HTTP Request): For each segment of the script, it sends an HTTP request to the ElevenLabs API to convert the text into speech, utilizing different voices as defined in the sheet.
  4. Uploads Audio to Google Drive: The generated audio files are then uploaded to a designated folder in Google Drive.
  5. Processes with Custom Code: A Code node is included, likely for custom logic, data manipulation, or formatting of the data before or after interacting with the APIs.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Account: An active n8n instance (cloud or self-hosted).
  • Google Account: With access to Google Sheets and Google Drive.
    • Google Sheets Credential: Configured in n8n to allow reading from your spreadsheet.
    • Google Drive Credential: Configured in n8n to allow uploading files.
  • ElevenLabs Account: An ElevenLabs API key for text-to-speech generation. This will be used in the HTTP Request node.
  • Google Sheet: A spreadsheet structured with your podcast script, including columns for speaker and text.
  • Google Drive Folder: A specific folder in Google Drive where the generated audio files will be stored.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets Node: Select or create a Google Sheets OAuth2 credential. Specify the Spreadsheet ID and the sheet name where your podcast script resides.
    • HTTP Request Node: Configure this node to interact with the ElevenLabs API. You will need to set the API endpoint, headers (including your ElevenLabs API key), and the request body to send the text and voice ID for synthesis.
    • Google Drive Node: Select or create a Google Drive OAuth2 credential. Specify the Folder ID where you want to save the audio files.
  3. Review and Customize the Code Node (ID 834): Examine the JavaScript code in the Code node. This node is likely used for transforming data, preparing the payload for ElevenLabs, or handling responses. Adjust it according to your specific data structure and requirements.
  4. Prepare your Google Sheet: Ensure your Google Sheet has the necessary columns (e.g., "Speaker", "Text") that the workflow expects. The Code node will likely reference these.
  5. Execute the Workflow: Click the "Execute workflow" button on the Manual Trigger node to run the workflow.

This workflow provides a robust foundation for automating multi-speaker podcast creation, significantly reducing manual effort and production time.

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