YouTube to Google Docs, summaries saved automatically
You finally find a great YouTube video… and then lose the best parts because the notes are scattered, half-finished, or stuck in a browser tab you’ll never reopen. Copy-pasting timestamps. Rewriting quotes. Trying to remember the “one important lesson” you wanted to share. It’s a grind.
YouTube summary automation fixes that mess. Marketers use it to pull insights for briefs and content angles. Students use it to study faster. And consultants doing research-heavy work stop living in Notion tabs and screenshots.
This workflow takes a YouTube link, grabs the transcript via Supadata, summarizes it with an AI model, then saves the final output into Google Docs in the Drive folder you choose. You’ll see exactly how it works, what you need, and what to tweak so the summaries match your style.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: YouTube to Google Docs, summaries saved automatically
flowchart LR
subgraph sg0["Chat Input Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Chat Input Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Assign Supadata Key", pos: "b", h: 48 }
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Fetch YouTube Transcript"]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Expand Transcript Rows", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Combine Transcript Text", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "Generate Summary Prompt", pos: "b", h: 48 }
n6@{ icon: "mdi:brain", form: "rounded", label: "Gemini Flash Model", pos: "b", h: 48 }
n7@{ icon: "mdi:cog", form: "rounded", label: "Create Doc Summary", pos: "b", h: 48 }
n4 --> n5
n3 --> n4
n6 -.-> n5
n1 --> n2
n0 --> n1
n2 --> n3
n5 --> n7
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n5 ai
class n6 aiModel
class n2 api
classDef customIcon fill:none,stroke:none
class n2 customIcon
Why This Matters: YouTube knowledge gets lost fast
Video is dense. A single 25-minute interview can contain five ideas you want to steal (ethically), two stats worth quoting, and a story you’ll want to retell in a client meeting. But the moment you try to capture it manually, everything slows down. You pause, rewind, type a few lines, then give up and tell yourself you’ll “summarize later.” Later never comes. And when you do come back, you can’t search your memory. You need a doc you can skim, share, and reuse.
It adds up fast. Here’s where it breaks down in real life.
- You end up rewatching the same sections because your notes don’t include the exact phrasing or context.
- Key takeaways get trapped in personal notebooks, so teammates can’t reuse them for campaigns, lessons, or client work.
- Manual copy-paste introduces small mistakes, which is how quotes and “facts” quietly get distorted.
- The effort feels too high for “just one video,” so you stop doing it consistently.
What You’ll Build: YouTube transcript-to-summary docs in Google Drive
This automation starts when you send a YouTube link into an n8n chat-style trigger (you can run it from a simple chat input, and many teams later swap it for Telegram or a webhook). n8n passes your Supadata API key, calls Supadata to fetch the video transcript, and then cleans the transcript into one readable text block. From there, an AI prompt turns that raw transcript into a structured summary, including the most important lessons and a few interesting facts that are easy to quote. Finally, the workflow creates a brand-new Google Doc inside the Drive folder you choose, so the output is searchable and shareable instead of living in someone’s clipboard.
The flow is simple: link in, transcript out, summary generated, doc created. The “middle” is where the magic happens, because combining transcript chunks into one clean input makes the AI output dramatically more usable.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you capture takeaways from 5 YouTube videos a week for content research. Manually, you might spend about 30 minutes per video between rewinding, typing, and cleaning up notes, so that’s roughly 2–3 hours weekly. With this workflow, you paste a link, wait for the transcript and AI to run, and the Google Doc appears in your Drive folder; your active time is closer to 5 minutes per video. For most teams, that’s a couple hours back every week, plus cleaner notes you’ll actually reuse.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Supadata for YouTube transcript retrieval
- Google Drive to create and store Google Docs
- Supadata API key (get it from your Supadata dashboard)
Skill level: Beginner. You’ll connect accounts, paste an API key, and choose which AI model to use.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
You provide a YouTube link. The workflow begins from a chat input trigger, where you submit the URL you want summarized. One link per run keeps it clean.
Supadata fetches the transcript. n8n inserts your Supadata API key, then makes an HTTP request to retrieve transcript data for that video. If the transcript is available, you get a structured response with multiple rows or chunks.
The transcript gets combined into one text. n8n expands the transcript rows and aggregates them into a single block, which is much easier for an AI model to understand and summarize consistently.
Your AI model generates the summary. A prompt template (“Process transcript to summary”) tells the model what format you want, including key lessons and interesting facts. This workflow uses an OpenRouter chat model node (Gemini Flash), but you can swap in your preferred LLM.
A Google Doc is created automatically. The final text is sent to Google Drive, which creates a new document in the folder you choose. File naming defaults to “transcript” plus date/time, but that’s easy to change.
You can easily modify the prompt format to match your voice and change the Google Drive folder based on project or client. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
Set up the incoming chat input that supplies the YouTube URL used to fetch the transcript.
- Add the Chat Input Trigger node as the workflow entry point.
- Keep the default Options configuration unless you need custom chat behavior.
- Confirm the workflow starts with Chat Input Trigger → Assign Supadata Key as shown in the connections.
Step 2: Connect the Transcript Fetch Request
Configure the Supadata API key and the HTTP request that retrieves the YouTube transcript.
- In Assign Supadata Key, set the assignment supadatakey to your API key value (currently the Value is
- Open Fetch YouTube Transcript and set URL to
=https://api.supadata.ai/v1/youtube/transcript?url={{ $('Chat Input Trigger').item.json.chatInput }}. - In Fetch YouTube Transcript, enable Send Headers and set header x-api-key to
={{ $json.supadatakey }}. - Confirm the connection path: Assign Supadata Key → Fetch YouTube Transcript → Expand Transcript Rows.
Step 3: Prepare and Combine Transcript Text
Split transcript entries into rows and aggregate them into a single text block for summarization.
- In Expand Transcript Rows, set Field to Split Out to
content. - In Combine Transcript Text, aggregate the Field to Aggregate as
text. - Verify the flow: Expand Transcript Rows → Combine Transcript Text → Generate Summary Prompt.
Step 4: Set Up the AI Summary Generation
Configure the summarization prompt and connect the LLM used to generate the markdown summary.
- Open Generate Summary Prompt and set Prompt Type to
define. - Set the Text prompt to:
=Below is a transcript of a youtube video. \nPlease summarize this, following these rules for your output:\n1. NEVER change the tenor of the text\n2. Get the best lessons from this transcript, as if you are a teacher or trainer. \n3. Summarize this with the following parts: Brief summary of the transcript, lessons learned in bullet points, interesting facts mentioned in bullet points. \n\nALWAYS put your output in markdown. \n\nTranscript:\n{{ $json.text }} - Ensure Gemini Flash Model is connected as the language model for Generate Summary Prompt.
- Credential Required: Connect your openRouterApi credentials in Gemini Flash Model.
text field correctly before it reaches Generate Summary Prompt.Step 5: Configure the Output Document
Create a Google Doc in Drive with the AI-generated summary content.
- Open Create Doc Summary and set Operation to
createFromText. - Set Name to
=transcript {{ $now }}. - Set Content to
={{ $json.text }}. - Select the target Drive as
My Driveand choose a Folder (currentlyn8n). - Credential Required: Connect your googleDriveOAuth2Api credentials in Create Doc Summary.
Step 6: Test and Activate Your Workflow
Run a full test to validate the transcript fetch, summarization, and document creation.
- Click Execute Workflow and submit a YouTube URL through Chat Input Trigger.
- Verify Fetch YouTube Transcript returns transcript content and Combine Transcript Text outputs a single combined
textfield. - Confirm Generate Summary Prompt produces a markdown summary and Create Doc Summary creates a new Google Doc in your target folder.
- When the output looks correct, toggle the workflow to Active for production use.
Troubleshooting Tips
- Supadata requests will fail if your API key is wrong or out of quota. Check the Supadata dashboard first, then update the key in the “Assign Supadata Key” node.
- If you’re seeing blank or partial summaries, the transcript response may be chunked differently than expected. Confirm the “Expand Transcript Rows” and “Combine Transcript Text” steps are receiving data before the AI step runs.
- Google Drive errors usually come from missing permissions or an expired OAuth connection. Reconnect Google Drive credentials in n8n, then verify the target folder still exists and is accessible.
Quick Answers
About 30 minutes if you already have Supadata and Google Drive ready.
No. You’ll paste an API key, connect Google Drive, and tweak the prompt if you want a different summary style.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Supadata and your LLM provider’s usage costs.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. The main lever is the “Generate Summary Prompt” step, where you can request action items, a study guide, a client-ready brief, or even a strict outline. You can also swap the “Gemini Flash Model” for another LLM provider inside n8n if you prefer. And if you want a different naming convention, change it in the Google Drive “Create Doc Summary” node.
Usually it’s an invalid API key or you’ve hit a usage limit. Regenerate your Supadata key (or check your plan), then update it in the “Assign Supadata Key” node. If the key is fine, confirm the YouTube URL is valid and the video actually has transcript data available. Occasionally, the HTTP request settings get edited accidentally, so compare your node configuration to the template.
A lot, as long as your API limits can keep up. On n8n Cloud, your execution quota depends on the plan; if you self-host, you’re mainly limited by your server and third-party rate limits. Practically, most people run dozens or hundreds of summaries a month without thinking about it, then upgrade when the library becomes core to their process.
Often, yes, because transcript cleanup and AI prompting usually need more than a simple two-step Zap. n8n makes it easier to expand transcript rows, aggregate them into one input, and then route outputs without paying extra for every branch. You also get a self-host option, which is handy when volume grows. Zapier or Make can still work if you only want “link in, summary out” with minimal formatting. If you want help choosing, Talk to an automation expert.
Once this is running, your best video takeaways stop evaporating. The workflow handles the repetitive part, and you get a clean Google Doc you can actually use.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
