Back to Catalog

YouTube transcription & translation to Google Docs with Gemini AI

WeblineIndiaWeblineIndia
1658 views
2/3/2026
Official Page

YouTube Transcription, Summarization & Translation to Google Docs

This workflow automates the end-to-end process of converting YouTube videos into structured, multilingual written content. It transcribes the video's speech, optionally summarizes it, translates it into the chosen language and stores the result in a well-formatted Google Doc—ready for review, sharing or publication.

Who’s It For

  • Content creators and bloggers repurposing video content.
  • Educators and researchers converting lectures into readable notes.
  • Marketing teams localizing video material for international audiences.
  • Students summarizing and translating study material.
  • YouTube viewers who want written notes or blog-ready formats.

How It Works

  1. A Webhook triggers the flow with inputs: youtube_url, language and enable_summary.
  2. A Code node formats these inputs into videoId, originalUrl, language and enable_summary.
  3. An HTTP Request node sends the video to Supadata API for full transcription.
  4. Another Code node combines all transcript segments into one body of text.
  5. The Basic LLM Chain node uses the Google Gemini Chat Model to summarize and translate the transcript if requested.
  6. A Google Docs node creates a new document with a title based on videoId and language.
  7. A final Google Docs node appends the processed summary and translation into the created document.

How to Set Up

  1. Webhook Input: Send a POST request with three fields: youtube_url, language, enable_summary.
  2. Configure Supadata API: Add the HTTP URL and Authorization Header for transcription.
  3. Set up Gemini Chat Model: Use Google Vertex AI/Gemini integration in the Basic LLM Chain node.
  4. Create Google Docs Credentials: Connect your Google account using OAuth2.
  5. Document Naming Logic: You may adjust document titles using expressions (e.g., {{ videoId }} - {{ language }}).

Requirements

  • Supadata API key (or any video-to-text API).
  • Google account with Google Docs access.
  • Google Gemini access via n8n’s LLM integration.
  • n8n Cloud or self-hosted instance.
  • Basic understanding of webhook setup (or a form frontend).

How to Customize

  • Change LLM model: Swap Gemini with GPT-4 or Claude in the LLM Chain node.
  • Summarization toggle: Use the enable_summary flag to control verbosity.
  • Document layout: Customize headings, font styles and content sections in Google Docs.
  • Multiple languages: Extend the workflow to translate into multiple languages and generate one document per language.
  • Sharing options: Add Gmail or Slack nodes to notify users once the document is generated.

Add‑ons

  • Notion Export: Send the document summary directly into Notion using the Notion node.
  • Slack Notification: Notify your team with a link to the Google Doc using the Slack node.
  • Google Sheets Logging: Log video URLs, timestamps, and language used for auditing.
  • n8n Forms Integration: Allow users to submit video URLs and language via a hosted n8n form.

Use Case Examples

  • Repurposing Videos into Blogs: Automatically convert YouTube podcasts into multilingual blog posts.
  • Educational Notes: Extract and translate lecture content into shareable study documents.
  • International Marketing Teams: Summarize and localize product explainer videos for different countries.
  • Transcription Library: Create a searchable database of translated transcripts from niche educational YouTube channels.

Common Troubleshooting

| Issue | Possible Cause | Solution | | ------------------------------- | ------------------------------------------ | ---------------------------------------------------------- | | Webhook not triggering | Incorrect webhook URL or POST format | Double-check payload and content-type (application/json) | | Transcription API fails | Invalid video ID or API key | Validate YouTube URL and Supadata API access | | Empty translation/summarization | Transcript was empty or prompt was weak | Ensure the video contains spoken content and refine prompt | | Google Doc not created | OAuth2 credentials not authorized properly | Reconnect Google Docs credentials in n8n | | Gemini LLM Chain fails | Model misconfigured or request malformed | Verify your model selection and payload structure |

Need Help?

Need help getting this set up or customizing it for your workflow?

✅ We can help you:

  • Set up transcription and translation APIs
  • Modify the summarization prompt
  • Customize document layouts or automate sharing

👉 Contact WeblineIndia's automation experts !

YouTube Transcription & Translation to Google Docs with Gemini AI

This n8n workflow automates the process of transcribing YouTube video content, translating it using Google Gemini AI, and saving the results into a Google Docs document. It's designed to streamline content repurposing and accessibility for video creators or researchers.

What it does

This workflow performs the following steps:

  1. Receives YouTube Video URL: It starts by listening for a webhook trigger, expecting a YouTube video URL as input.
  2. Fetches YouTube Transcript: It makes an HTTP request to an external API (likely a YouTube transcription service) to retrieve the transcript of the provided YouTube video.
  3. Prepares Transcript for AI: A Code node processes the raw transcript, cleaning and formatting it for optimal input into the AI model.
  4. Translates with Google Gemini AI: It utilizes the Google Gemini Chat Model via a Basic LLM Chain to translate the prepared transcript into a specified target language.
  5. Creates Google Doc: Finally, it creates a new Google Docs document and inserts the original transcript and the translated version.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • YouTube Transcription API Key/Endpoint: An API endpoint or service capable of extracting YouTube video transcripts. This is configured in the "HTTP Request" node.
  • Google Account: A Google account with access to Google Docs for creating and saving documents.
  • Google Gemini API Key: Access to the Google Gemini AI model, configured within the "Google Gemini Chat Model" node.
  • n8n Credentials: Appropriate n8n credentials for Google Docs and Google Gemini API.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Docs: Set up your Google account credentials for the Google Docs node.
    • Google Gemini Chat Model: Configure your Google Gemini API key as a credential for the "Google Gemini Chat Model" node.
  3. Configure HTTP Request:
    • Update the "HTTP Request" node with the correct URL and any necessary authentication for your chosen YouTube transcription service.
  4. Activate Webhook: Activate the "Webhook" node to get its unique URL. This URL will be used to trigger the workflow.
  5. Trigger the Workflow: Send a POST request to the webhook URL with the YouTube video URL in the request body (e.g., as JSON: {"youtubeUrl": "https://www.youtube.com/watch?v=YOUR_VIDEO_ID"}).
  6. Review Google Docs: The workflow will create a new Google Docs document containing the original and translated transcripts.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31