Analyze YouTube videos and auto-generate AI reports in Google Docs with DeepSeek

Name: Analyze YouTube videos and auto-generate AI reports in Google Docs with DeepSeek
Availability: InStock
Author: Pratyush Kumar Jha

Analyze YouTube videos and auto-generate AI reports in Google Docs with DeepSeek preview

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Overview

A compact n8n workflow that accepts a YouTube link or uploaded video, pulls a transcript via Supadata.ai, runs a language-model-based video analysis agent to produce a structured report, extracts a title/metadata, then creates and updates a Google Doc with the analysis. It's designed to automate transcription → analysis → document creation for fast, repeatable video reviews.

How it works

Trigger — Upload File or YouTube Link A form trigger receives a youtube_url or an uploaded file/webhook event.
Transcription — Transcription using Supadata.ai Calls the transcription API using the x-api-key header to retrieve the video transcript/text.
Analysis — Analyser The transcript is passed to the Analyser LangChain agent which runs a tailored prompt (expert video analyst) and generates a plain-text report.
Metadata extraction — File Name Detector The information extractor parses the analyser output to extract structured attributes such as the Title.
Aggregation & Merge Merge/Aggregate nodes combine the analysis and extracted fields into a single payload.
Document Creation Creating New File creates a Google Docs document using the extracted Title, and Updating Content in File inserts the analyser output into the document.
Optional Follow-ups Additional nodes can forward the document link, send it to Slack, or store metadata in a database.

Quick Setup Guide

👉 Demo & Setup Video 👉 Course

Nodes of interest

Upload File or YouTube Link formTrigger (webhook) — Entry point for user-supplied links or files.
Transcription using Supadata.ai httpRequest — Fetches transcript from https://api.supadata.ai/... and requires the x-api-key header.
OpenRouter Chat Model / OpenRouter Chat Model1 lmChatOpenRouter — Language model nodes connected to the Analyser and File Name Detector using the model deepseek/deepseek-r1-distill-llama-70b.
Analyser LangChain agent node that contains the expert analysis prompt and generates a full plain-text report from the transcript. Configuration includes hasOutputParser: true and retry enabled.
File Name Detector LangChain information extractor that extracts structured attributes like Title from the analysis output.
Merge / Aggregate Combines outputs from analysis and extraction into a single payload used for document creation.
Creating New File / Updating Content in File Google Docs nodes used to create and update documents using googleDocsOAuth2Api credentials.

What you’ll need (credentials)

OpenRouter account Used by OpenRouter Chat Model nodes. API key stored in the openRouterApi credential.
Supadata.ai API key Added in the HTTP header x-api-key in the transcription request.
Google Docs OAuth2 googleDocsOAuth2Api credential used for creating and updating Google Docs.
Optional integrations Slack webhook, Google Drive, or database credentials if adding notifications or persistent storage.

Recommended settings & best practices

Prompt control Keep the Analyser prompt explicit about required sections, output style, and how to handle missing transcripts.
Retries & timeouts Enable retries for long-running model or HTTP calls. Configure proper HTTP request timeouts.
Rate limits Respect transcription and model provider rate limits. Add throttling if needed.
Input validation Validate the youtube_url before processing and handle transcript failures gracefully.
Chunk transcripts Split long transcripts into chunks before sending to the LLM to avoid context limit issues.
Logging & audit Store transcripts, analysis results, and metadata for debugging and traceability.
Security Store API keys as n8n credentials rather than plaintext.
Document naming Sanitize the extracted Title to prevent invalid filename characters.
Monitoring Add error notifications via email or Slack for failed runs.

Customization ideas

Alternative transcription providers Replace Supadata.ai with AssemblyAI, Whisper (self-hosted), or YouTube captions.
Multiple output formats Export results to Google Docs, PDF, or JSON metadata.
Speaker diarization Include speaker labels and timestamps in the analysis.
Summaries & highlights Add TL;DR summaries and timestamped key moments.
Content classification Use additional LLM nodes to detect sentiment, category, or compliance issues.
Thumbnail generation Capture frames from the video to generate thumbnails.
Webhook callbacks Send the document link to Slack, email, or other systems.
Model routing Use smaller models for short videos and higher-quality models for long videos.
Human review pipeline Create a review queue for manual verification before publishing results.

Complexity

intermediate

Published 05 Mar 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13887/13887.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Create fillable document templates from PDF or DOCX with GPT-4o and Google Drive

## 📄Template Creator ### How it works This workflow accepts any uploaded document (PDF or DOCX) via webhook and automatically converts it into a reusable fill-in-the-blank template. **Step 1 — Identify:** GPT-4o first reads the document and determines the document type (e.g., Employment Contract, Invoice, NDA, Lease Agreement, Project Proposal) and the specific variable fields that type of document typically contains. **Step 2 — Templatize:** A second AI pass uses the identified document type and field list to replace all variable content with clearly labeled `[BRACKET]` placeholders while preserving all static boilerplate and structure verbatim. **Step 3 — Deliver:** The cleaned template is rendered to PDF via Gotenberg, uploaded to Google Drive, made publicly accessible, and a JSON response with file URLs is returned to the caller. ### Setup 1. Configure the **Webhook** path if needed (default: `general-template-creator`) 2. Set your **OpenAI** credential on both LLM nodes 3. Set your **Google Drive** credential and confirm the target folder ID in the Upload node 4. Confirm the **Gotenberg** URL matches your self-hosted instance 5. Install the community node `n8n-nodes-word2text` (see ⚠️ warning sticky) ### Customization - Swap GPT-4o for GPT-4.1 or GPT-4.1-mini on the Identify node to reduce cost on the lighter classification task - Add a Switch node after identification to route different document types to type-specific prompts - Modify the Drive folder ID to sort templates into subfolders by document type Document accepts input from a form such as the one found here: [Sample Form](https://iportgpt.com/n8n_assets/template_creator_form.html)

View

Generate PDF pricing proposals from Excel with Gotenberg and Outlook

## How it works 1. **Webhook Trigger** — A web form POSTs prospect details, selected services, discount level, and requestor info to the webhook endpoint. 2. **Fetch Pricing Sheet** — Retrieves all rows from your `pricing_request.xlsx` Excel table in OneDrive/SharePoint. 3. **Process & Price** — Filters the pricing rows to the selected services, applies the correct Discount / Retail / Premium price tier, and calculates the total. 4. **Build HTML** — Renders a fully branded HTML proposal document with cover info, line-item pricing table, terms, and a signature block. 5. **Convert to PDF** — Sends the HTML to a self-hosted [Gotenberg](https://gotenberg.dev) instance, which returns a print-ready PDF. 6. **Email Proposal** — Delivers the PDF as an attachment via Gmail OAuth2 to the requester and any internal recipients you configure.

View

Classify and route email attachments with easybits, Gmail and Google Drive

## What This Workflow Does Receive any business document via email. The attachment is automatically **classified** (Invoice, Contract, or Purchase Order) using easybits Extractor, then **routed** down the correct path where a second Extractor pulls out document-specific data. Each route stores the file in Google Drive and triggers the appropriate action – Invoices go to a finance spreadsheet, Contracts and Purchase Orders trigger Slack notifications. ## How It Works 1. **Receive** – Gmail polls for new emails with attachments every minute 2. **Classify** – easybits Extractor identifies the document type and returns a class label 3. **Route** – A Switch node sends the item down the matching path (Invoice / Contract / PO) 4. **Merge Binary** – The original file is merged back into the routed item (classification strips the binary) 5. **Extract** – A second easybits Extractor pulls fields specific to that document type 6. **Merge Data + File** – Extracted JSON and original binary are combined for upload 7. **Store & Notify** – The file is uploaded to Google Drive; Invoices update a spreadsheet, Contracts and POs trigger Slack alerts --- ## Setup Guide ### 1. Create Your easybits Classification Pipeline 1. Go to **extractor.easybits.tech** and create a new pipeline 2. Add **one field** called `document_class` 3. In the field prompt, describe your classification categories and how to identify each one (see the "easybits: Classify Document" node for a reference prompt) 4. The prompt should instruct the model to return exactly one category label – no explanations, no extra text 5. Adjust the categories and identification criteria to match your specific document types 6. Copy your **Pipeline ID** and connect the credential in the classification node > 💡 **Tip:** The classification prompt is the heart of this workflow. The more specific your category descriptions and decision rules are, the more accurate your results will be. ### 2. Create Three Extraction Pipelines Create one pipeline per document type on **extractor.easybits.tech**: - **Invoice pipeline** – fields: `invoice_number`, `total_amount`, `currency`, `due_date`, `vendor_name` - **Contract pipeline** – fields: `client_name`, `contract_type`, `contract_value`, `currency`, `start_date`, `notice_period` - **Purchase Order pipeline** – fields: `supplier_name`, `po_number`, `order_date`, `expected_delivery_date`, `total_amount`, `currency` Connect each pipeline's credentials to the matching Extractor node. ### 3. Set Up Gmail Connect your Gmail account via OAuth2. Optionally filter by label to only process specific emails. Make sure **Download Attachments** is enabled in the node options. ### 4. Set Up Google Drive Create three folders in Google Drive: **Invoices**, **Contracts**, **Purchase Orders**. Select the correct folder in each Upload node. Set the **Input Binary Field** to `attachment_0` (or whichever field carries the PDF). ### 5. Set Up Google Sheets Create a spreadsheet (or use an existing Master Finance File). Make sure the column headers match the field mappings in the "Update Master Finance Sheet" node. ### 6. Set Up Slack Connect your Slack workspace. Select the channel for contract notifications (e.g. `#contracts`) and the channel for PO updates (e.g. `#operations`). Adjust the message templates if your extracted field names differ. ### 7. Activate & Test Set the workflow to active and send a test email with an invoice, contract, and purchase order attached to verify each route works end to end.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Analyze YouTube videos and auto-generate AI reports in Google Docs with DeepSeek

Workflow preview

Overview

How it works

Quick Setup Guide

Nodes of interest

What you’ll need (credentials)

Recommended settings & best practices

Customization ideas

Tags