Extract YouTube Video Metadata and Save to Google Docs using RapidAPI
πΊ Automated YouTube Video Metadata Extraction Workflow
Description: This workflow leverages the YouTube Metadata API to automatically extract detailed video information from any YouTube URL. It uses n8n to automate the entire process and stores the metadata in a neatly formatted Google Docs document.
Perfect for content creators, marketers, and researchers who need quick, organized YouTube video insights at scale.
βοΈ Node-by-Node Explanation
1. β On Form Submission
This node acts as the trigger. When a user submits a form containing a YouTube video URL, the workflow is activated.
- Input: YouTube Video URL
- Platform:
Webhookorn8n Form Trigger
2. π YouTube Metadata API (HTTP Request)
This node sends the video URL to the YouTube Metadata API via HTTP request.
-
Action:
GETrequest -
Headers:
-H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: youtube-metadata1.p.rapidapi.com" -
Endpoint Example:
https://youtube-metadata1.p.rapidapi.com/video?url=YOUTUBE_VIDEO_URL -
Output: JSON with metadata like:
- Title
- Description
- Views, Likes, Comments
- Duration
- Upload Date
- Channel Info
- Thumbnails
3. π§ Reformat Metadata (Code Node)
This node reformats the raw metadata into a clean, human-readable text block.
-
Example Output Format:
π¬ **Title:** How to Build Workflows with n8n π§Ύ **Description:** This tutorial explains how to build... π€ **Channel:** n8n Tutorials π **Published On:** 2023-05-10 β±οΈ **Duration:** 10 minutes, 30 seconds ποΈ **Views:** 45,678 π **Likes:** 1,234 π¬ **Comments:** 210 π **URL:** https://youtube.com/watch?v=abc123
4. π Append to Google Docs
This node connects to your Google Docs and appends the formatted metadata into a selected document.
-
Document Format Example:
## π Video Entry β [Date] π¬ **Title:** π§Ύ **Description:** π€ **Channel:** π **Published On:** β±οΈ **Duration:** ποΈ **Views:** π **Likes:** π¬ **Comments:** π **URL:** ---
π Use Cases
- Content Creators: Quickly analyze competitor content or inspirations.
- Marketers: Collect campaign video performance data.
- Researchers: Compile structured metadata across videos.
- Social Media Managers: Create content briefs effortlessly.
β Benefits
- π Time-saving: Automates manual video data extraction
- π Accurate: Uses reliable, updated YouTube API
- π Organized: Formats and stores data in Google Docs
- π Scalable: Handles unlimited YouTube URLs
- π― User-friendly: Simple setup and clean output
π How to Get Your API Key for YouTube Metadata API
- Go to the YouTube Metadata API on RapidAPI.
- Sign up or log in to your RapidAPI account.
- Click Subscribe to Test and choose a pricing plan (free or paid).
- Copy your API Key shown in the "X-RapidAPI-Key" section.
- Use it in your HTTP request headers.
π§° Google Docs Integration β Full Setup Instructions
π Step 1: Enable Google Docs API
- Go to the Google Cloud Console.
- Create a new project or select an existing one.
- Navigate to APIs & Services > Library.
- Search for Google Docs API and click Enable.
- Also enable Google Drive API (for document access).
π Step 2: Create OAuth Credentials
- Go to APIs & Services > Credentials.
- Click Create Credentials > OAuth Client ID.
- Select Web Application or Desktop App.
- Add authorized redirect URIs if needed (e.g., for n8n OAuth).
- Save your Client ID and Client Secret.
π Step 3: Connect n8n to Google Docs
- In n8n, go to Credentials > Google Docs API.
- Add new credentials using the Client ID and Secret from above.
- Authenticate with your Google account and allow access.
π Step 4: Create and Format Your Google Document
-
Go to Google Docs and create a new document.
-
Name it (e.g.,
YouTube Metadata Report). -
Optionally, add a title or table of contents.
-
Copy the Document ID from the URL:
https://docs.google.com/document/d/DOCUMENT_ID/edit
π Step 5: Use Append Content to Document Node in n8n
-
Use the
Google Docsnode in n8n with:- Operation:
Append Content - Document ID: Your copied Google Doc ID
- Content: The formatted video summary string
- Operation:
π¨ Customization Options
- π‘ Add Tags: Insert hashtags or categories based on video topics.
- π Organize by Date: Create headers for each day or weekβs entries.
- πΈ Embed Thumbnails: Use
thumbnail_urlto embed preview images. - π Spreadsheet Export: Use Google Sheets instead of Docs if preferred.
π Troubleshooting Tips
| Issue | Solution |
| ------------------------------ | ------------------------------------------------------------------- |
| β Auth Error (Google Docs) | Ensure correct OAuth redirect URI and permissions. |
| β API Request Fails | Check API key and request structure; test on RapidAPI's playground. |
| π Doc Not Updating | Verify Document ID and sharing permissions. |
| π§Ύ Bad Formatting | Debug the code node output using logging or console in n8n. |
| π n8n Timeout | Consider using Wait or Split In Batches for large submissions. |
π Ready to Launch?
You can deploy this workflow in just minutes using n8n.
π Start Automating with n8n
Extract YouTube Video Metadata and Save to Google Docs
This n8n workflow automates the process of extracting metadata from YouTube videos using the RapidAPI YouTube V3 API and then saving that information into a Google Doc. It's triggered by a form submission, making it easy to integrate into various data collection or content management processes.
What it does
This workflow performs the following steps:
- Triggers on Form Submission: It waits for a form submission, which is expected to contain a YouTube video ID.
- Fetches YouTube Video Metadata: It makes an HTTP request to the RapidAPI YouTube V3 API, using the provided video ID to retrieve detailed metadata about the YouTube video.
- Processes API Response: A Code node then processes the raw JSON response from the API, extracting key pieces of information such as the video title, description, channel title, view count, like count, and publish date.
- Creates Google Doc Content: It formats the extracted video metadata into a structured text string suitable for a Google Doc.
- Appends to Google Doc: Finally, it appends this formatted metadata as a new paragraph to a specified Google Doc.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- RapidAPI Account: An account with RapidAPI and a subscription to the YouTube V3 API. You will need your RapidAPI Host and Key.
- Google Account: A Google account with access to Google Docs.
- Google Docs Credential: An n8n credential configured for Google Docs (OAuth2 recommended).
- Google Doc ID: The ID of the Google Doc where you want to append the video metadata.
Setup/Usage
- Import the Workflow:
- Download the workflow JSON.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure Credentials:
- HTTP Request (RapidAPI):
- Edit the "HTTP Request" node.
- Under "Headers", ensure
x-rapidapi-hostandx-rapidapi-keyare correctly set with your RapidAPI host and key for the YouTube V3 API.
- Google Docs:
- Edit the "Google Docs" node.
- Select or create a new "Google Docs API" credential. This will typically involve authenticating with your Google account and granting n8n the necessary permissions to manage Google Docs.
- HTTP Request (RapidAPI):
- Configure Google Doc ID:
- In the "Google Docs" node, set the "Document ID" to the ID of the Google Doc you wish to update. You can find this in the URL of your Google Doc (e.g.,
https://docs.google.com/document/d/YOUR_DOCUMENT_ID/edit).
- In the "Google Docs" node, set the "Document ID" to the ID of the Google Doc you wish to update. You can find this in the URL of your Google Doc (e.g.,
- Configure Form Trigger:
- Edit the "On form submission" node.
- The form is expected to send a
videoIdfield in its payload. Ensure your form submission mechanism sends data in this format. - Activate the workflow.
- Test the Workflow:
- Submit your form with a valid YouTube video ID.
- Check the execution history in n8n and your Google Doc to confirm the metadata was extracted and appended correctly.
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.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte