HumationHuman + Automation
Back to Catalog

Generate multispeaker podcast 🎙️ with AI natural-sounding 🤖🧠 & Google Sheets

DavideDavide
2042 views
2/3/2026
NotificationGoogle DriveAutomationFilesEmail
Official Page

This workflow automates the generation of multi-speaker podcasts using AI-powered text-to-speech technology. It starts by retrieving a podcast script from a Google Sheets document, where each speaker’s lines are clearly defined. The workflow then processes the script, generates a natural-sounding audio file with different voices for each speaker, and stores the final audio file in Google Drive.

The workflow is designed to save time and resources by automating the podcast production process, making it ideal for content creators, marketers, and businesses that need to produce high-quality audio content regularly.

How It Works

  1. Triggering the Workflow:

    • The workflow starts with the When clicking ‘Test workflow’ node, which can be triggered manually to begin the process.

  2. Data Retrieval:

    • The Get Podcast text node retrieves data from a Google Sheets document containing the podcast script. The document includes columns for the speaker's name and the corresponding text.

  3. Data Aggregation:

    • The Get all rows node aggregates the data from the Google Sheets document, combining the speaker names and their respective text into a single dataset.

  4. Text Formatting:

    • The Full Podcast Text node processes the aggregated data, formatting it into a single string where each speaker's text is prefixed with their name.

  5. Audio Generation:

    • The Create Audio node sends a request to the API to generate a multi-speaker podcast audio file. The request includes the formatted text and specifies the voices for each speaker. When you register for the API service you will get 1$ for free. For continuous work add API credits to your account.

  6. Status Check:

    • The Get status node checks the status of the audio generation request. If the status is "COMPLETED", the workflow proceeds; otherwise, it waits again.

  7. Audio Retrieval:

    • The Get Url Audio node retrieves the URL of the generated audio file.
    • The Get File Audio node downloads the audio file from the provided URL.

  8. Audio Storage:

    • The Upload Audio node uploads the generated audio file to a specified Google Drive folder for storage.

Key Features

  • Multi-Speaker Support: Generates podcasts with different voices for each speaker, creating a more dynamic and engaging listening experience.
  • Google Sheets Integration: Retrieves podcast scripts from a Google Sheets document, making it easy to manage and update content.
  • AI-Powered Text-to-Speech: Uses advanced AI models to generate natural-sounding audio from text.
  • Automated Audio Generation: Streamlines the process of creating podcast audio files, reducing the need for manual recording and editing.
  • Google Drive Storage: Automatically uploads the generated audio files to Google Drive for easy access and sharing.

This workflow is ideal for businesses and content creators looking to automate the production of multi-speaker podcasts. It leverages AI to handle the complex task of generating natural-sounding audio, allowing users to focus on creating compelling content.

Need help customizing?

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

n8n Podcast Generation Workflow

This n8n workflow automates the process of generating multi-speaker, natural-sounding podcasts based on content provided in a Google Sheet. It uses AI for text-to-speech generation and organizes the resulting audio files in Google Drive.

Description

This workflow streamlines the creation of podcasts by taking structured content from a Google Sheet, processing it to generate audio for multiple speakers, and then storing the final audio files in Google Drive. It includes logic to handle different speaker segments and ensures a smooth, automated production pipeline for your podcast episodes.

What it does

  1. Triggers Manually: The workflow is initiated manually when you click "Execute workflow".
  2. Reads Podcast Data from Google Sheets: It connects to a specified Google Sheet to retrieve the podcast script, including speaker information and their respective dialogue.
  3. Processes Each Podcast Segment: It iterates through each row (segment) of the podcast data from the Google Sheet.
  4. Filters for Speaker Segments: For each segment, it checks if a "Speaker" column is defined.
  5. Generates Audio for Each Speaker:
    • If a speaker is identified, it makes an HTTP Request to an external AI text-to-speech service (e.g., Google Text-to-Speech, ElevenLabs, etc. – the specific service is not explicitly defined in the JSON but inferred by the HTTP Request and the workflow name).
    • It sends the speaker's text and potentially a voice ID to the AI service.
    • It waits for a short duration (1 second) after each audio generation, likely to avoid rate limits or ensure service stability.
  6. Aggregates Audio Segments: After processing all speaker segments, it combines the generated audio files.
  7. Uploads Audio to Google Drive: The final aggregated audio file (or individual segment files, depending on the HTTP Request node's output) is uploaded to a specified folder in Google Drive.
  8. Handles Non-Speaker Segments: If a segment does not have a speaker defined, it proceeds without generating audio (this path is currently not fully defined in the provided JSON, but the If node implies this branching).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Sheets Account: Access to a Google Sheets document containing your podcast script.
  • Google Drive Account: A Google Drive account where the generated podcast audio files will be stored.
  • AI Text-to-Speech Service: An API key and access to an AI text-to-speech service (e.g., Google Text-to-Speech, ElevenLabs, AWS Polly, etc.) capable of generating natural-sounding, multi-speaker audio. The HTTP Request node will need to be configured for this service.
  • n8n Credentials: Configured n8n credentials for Google Sheets, Google Drive, and your chosen AI Text-to-Speech service (if it uses API Key authentication).

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Google Sheets Node (ID: 18):
    • Select your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where your podcast script is located. Ensure your sheet has columns for "Speaker" and the text to be spoken.
  3. Configure HTTP Request Node (ID: 19):
    • Set up the Authentication method (e.g., API Key, OAuth) for your chosen AI text-to-speech service.
    • Configure the URL, Method (likely POST), and Body of the request to send the speaker's text and voice parameters to the AI service. You will need to use expressions to dynamically insert the speaker's text from the Google Sheets data.
    • Adjust the Response Format if necessary to correctly parse the audio data returned by the AI service.
  4. Configure Google Drive Node (ID: 58):
    • Select your Google Drive credential.
    • Specify the Folder ID where you want to upload the generated podcast audio files.
    • Configure the File Name and File Content (using an expression to reference the output of the Aggregate or HTTP Request node) for the uploaded audio.
  5. Configure Code Node (ID: 834):
    • This node likely contains logic to prepare the text for the AI service or process its response. Review and adjust the JavaScript code as needed for your specific AI service's API requirements and desired output.
  6. Activate the Workflow: Once configured, activate the workflow.
  7. Execute the Workflow: Click "Execute workflow" in the n8n editor to run the podcast generation 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