HumationHuman + Automation
Back to Catalog

Translate 🎙️and upload dubbed YouTube videos 📺 using ElevenLabs AI Dubbing

DavideDavide
159 views
2/3/2026
AWSS3AutomationSplitPDF
Official Page

This workflow automates the end-to-end process of video dubbing using ElevenLabs, storage on Google Drive, and publishing on Youtube.

This workflow is ideal for creators, agencies, and media teams that need to TRANSLATE process and publish large volumes of video content consistently.

For this workflow, I started from my Italian YouTube Short, and by applying the same workflow, the result was this English version.

Key Advantages

1. ✅ Full Automation of Video Localization

The entire process—from video download to AI dubbing and publishing—is automated, eliminating manual steps and reducing human error.

2. ✅ Fast Multilingual Content Scaling

With AI-powered dubbing, the same video can be quickly localized into different languages, enabling global audience expansion.

3. ✅ Efficient Time Management

The workflow intelligently waits for the dubbing process to finish using dynamic timing, avoiding unnecessary retries or failures.

4. ✅ Centralized Content Distribution

A single workflow handles storage, social posting, and YouTube uploads, simplifying content operations across platforms.

5. ✅ Reduced Operational Costs

Automating dubbing and publishing significantly lowers costs compared to manual voiceovers, video editing, and uploads.

6. ✅ Easy Customization & Reusability

Parameters like video URL, language, title, and platform can be easily changed, making the workflow reusable for different projects or clients.

How It Works

  1. The workflow begins with a manual trigger that sets input parameters: a video URL and the target language for dubbing (e.g., en for English).
  2. The video is fetched from the provided URL via an HTTP request.
  3. The video file is sent to the ElevenLabs Dubbing API, which initiates audio dubbing in the specified target language.
  4. The workflow then waits for a calculated duration (video length + 120 seconds) to allow the dubbing process to complete.
  5. After the wait, it checks the dubbing status using the dubbing_id and retrieves the final dubbed audio file.
  6. The dubbed video is then processed in parallel:
    • Uploaded to Google Drive in a designated folder.
    • Uploaded to Postiz for social media management.
    • Uploaded via Upload-Post.com API for YouTube publishing.
  7. Finally, the workflow triggers a Postiz node to schedule or publish the content to YouTube with the prepared metadata.

Set Up Steps

  1. Configure Input Parameters
    In the Set params node, define:

    • video_url: Direct URL to the source video.
    • target_audio: Language code (e.g., en, es, fr) for dubbing.

  2. Set Up Credentials
    Ensure the following credentials are configured in n8n:

  3. Adjust Wait Time
    Modify the Wait node if needed:
    expected_duration_sec + 120 ensures enough time for dubbing. Adjust based on video length.

  4. Customize Upload Destinations
    Update folder IDs (Google Drive) and platform settings (Upload-Post.com) as needed.

  5. Set Post Content
    In the Youtube Postiz and Youtube Upload-Post nodes, replace YOUR_CONTENT and YOUR_USERNAME with actual titles, descriptions, and channel details.

  6. Activate and Test
    Activate the workflow in n8n, click Execute workflow, and monitor execution for errors. Ensure all API keys and permissions are valid.

👉 Subscribe to my new YouTube channel. Here I’ll share videos and Shorts with practical tutorials and FREE templates for n8n.

image

Need help customizing?

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

n8n Workflow: Translate and Upload Dubbed YouTube Videos (using ElevenLabs AI Dubbing)

This n8n workflow provides a framework for automating the process of translating and dubbing YouTube videos using AI, and then uploading the dubbed versions. While the provided JSON is a starting point, it outlines the core components necessary for such an automation.

What it does

This workflow is designed to streamline the process of preparing and handling media for translation and dubbing. Specifically, it includes the following steps:

  1. Manual Trigger: The workflow is initiated manually, allowing for on-demand processing of videos.
  2. Edit Fields (Set): This node is typically used to manipulate or set data within the workflow. In this context, it would likely be used to prepare video metadata, URLs, or other relevant information for subsequent translation and dubbing steps.
  3. Google Drive: This node interacts with Google Drive, suggesting that the workflow might involve:
    • Uploading files: Storing original video files, translated scripts, or dubbed audio/video in Google Drive.
    • Downloading files: Retrieving video files or scripts from Google Drive for processing.
    • Managing files: Organizing translated content or dubbing outputs within Google Drive.
  4. HTTP Request: This is a versatile node for making API calls. In the context of "ElevenLabs AI Dubbing," this node would be crucial for:
    • Interacting with ElevenLabs API: Sending audio/video for dubbing, retrieving translated scripts, or fetching dubbed audio.
    • Interacting with YouTube API: Uploading the final dubbed video to YouTube.
    • Calling other translation/transcription services: If additional steps are involved before ElevenLabs.
  5. Wait: This node introduces a pause in the workflow, which can be useful for:
    • Rate limiting: Waiting between API calls to avoid hitting service limits.
    • Asynchronous operations: Allowing time for external services (like ElevenLabs) to process requests before checking for results.
    • Manual review points: Giving a user time to review intermediate outputs before the workflow proceeds.
  6. Sticky Note: This node is for documentation within the workflow itself, providing context or instructions for specific parts of the flow.

Prerequisites/Requirements

To effectively use and expand this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Google Drive Account: For storing and retrieving video-related files. You will need to configure Google Drive credentials in n8n.
  • ElevenLabs Account & API Key: For AI dubbing services. You will need to integrate with the ElevenLabs API using the HTTP Request node.
  • YouTube Account & API Key: For uploading the final dubbed videos. You will need to integrate with the YouTube API using the HTTP Request node.
  • Video Files: The source video files you intend to translate and dub.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Drive credentials within n8n.
    • Configure the HTTP Request nodes with your ElevenLabs API Key and YouTube API Key (once these nodes are configured to interact with those services).
  3. Customize Nodes:
    • The Edit Fields (Set) node will need to be configured to pass the necessary video information (e.g., YouTube URL, video ID, desired target language).
    • The HTTP Request nodes will need to be configured with the specific API endpoints and request bodies for ElevenLabs (dubbing) and YouTube (uploading). This will involve understanding the respective API documentation.
    • Adjust the Wait node's duration as needed based on the processing time of external services.
  4. Execute the Workflow: Trigger the workflow manually using the "When clicking ‘Execute workflow’" node.

This workflow provides a solid foundation. You would typically expand it by adding nodes for:

  • Extracting audio from YouTube videos.
  • Transcribing the original audio.
  • Translating the transcription.
  • Sending the translated text to ElevenLabs for dubbing.
  • Merging the dubbed audio with the original video.
  • Handling errors and notifications.

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