🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

YouTube to Telegram, instant TL;DW summaries

YouTube to Telegram, instant TL;DW summaries - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
YouTube to Telegram, instant TL;DW summaries - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You paste a YouTube link, tell yourself you’ll “watch it later,” and then… it sits there. Or you do watch it, but the notes are messy, the best quote is gone, and you can’t find the one tool they mentioned at minute 47.

This YouTube TL;DW automation hits marketing managers hardest during competitor research. But founders trying to learn fast and students turning lectures into study notes feel the same drag. The outcome is simple: structured, searchable summaries in Telegram without rewatching everything.

You’ll see how the workflow grabs the transcript, pulls video metadata, generates a clean TL;DW with chapters and quotes, and sends it back to Telegram in readable chunks.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: YouTube to Telegram, instant TL;DW summaries

The Problem: YouTube Research Eats Your Week

Watching long YouTube videos for “just one insight” is a trap. You start at 1.25x speed, pause to write notes, rewind because you missed a tool name, then lose your place when Slack pings. Later, when you need that exact framework or quote, you’re scrubbing the timeline again, hoping you remember the right chapter. It’s not only slow. It’s mentally expensive, and the work is weirdly fragile because your notes depend on you catching everything in real time.

It adds up fast. Here’s where it breaks down in real life.

  • Manual note-taking turns a 2-hour video into a half-day task once you include rewinding, formatting, and saving it somewhere useful.
  • Important details get lost, especially tool names, timestamps, and quotable lines that you want to reuse in content or internal docs.
  • Teams don’t share learnings well because one person’s notes live in Notion, another person’s are in a Google Doc, and the original link has no structure.
  • Existing “summarizer” tools often miss context because they don’t pull full transcripts and metadata reliably.

The Solution: Send a Link, Get a Structured TL;DW

This workflow turns Telegram into your “dropbox for video knowledge.” You send a YouTube URL to a Telegram bot, and n8n validates the link so you don’t waste time on bad inputs. Then it fetches the full transcript and the video’s metadata (title, channel, duration, tags, chapters, and more) through Decodo’s scraping API. Once the transcript is cleaned, Google Gemini Flash generates a structured TL;DW that’s actually usable, not a vague paragraph. Finally, the workflow merges the AI summary with the metadata, formats everything into Telegram-friendly chunks, and sends you a video overview plus the full summary in a clean sequence.

It starts with a Telegram message trigger. From there, transcript and metadata are pulled in parallel so you are not waiting on two slow steps in a row. The output lands back in Telegram as a readable overview and a TL;DW broken into messages that fit Telegram’s limits.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your agency reviews 50 competitor videos a month and each one averages about 90 minutes. Manually, even “skimming” and taking usable notes can take about 2 hours per video once you include pauses and rewinds, so you’re looking at roughly 100 hours. With this workflow, you drop each link into Telegram (maybe 1 minute each) and get the TL;DW back in about a minute. That’s still time spent reading, but most teams end up closer to 6–10 hours total for the month, not 100.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram Bot API for receiving links and replying.
  • Decodo Scraper API to extract transcripts and metadata.
  • Google Gemini API key (get it from Google AI Studio).

Skill level: Beginner. You’ll connect a few accounts, paste API keys, and edit one or two settings like language.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A Telegram message kicks it off. You send a youtube.com or youtu.be link to your bot, and the workflow checks it’s valid before doing anything expensive.

Transcript and metadata are collected in parallel. n8n extracts the video ID, then calls Decodo to fetch the transcript and video details at the same time, so the wait is usually short.

The summary gets generated and structured. The transcript is cleaned, then Gemini Flash creates the TL;DW with chapters, key points, tools mentioned, practical takeaways, and notable quotes.

Telegram receives a neat, readable output. The workflow merges the summary with metadata, formats it into chunks (so messages don’t get cut off), throttles delivery slightly, and posts both the overview card and the full TL;DW.

You can easily modify the summary format to match your note style (or your team’s template) based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Message Trigger

Set up the workflow to start when a Telegram message is received and validate incoming YouTube links.

  1. Add Telegram Message Trigger and enable updates for message.
  2. Credential Required: Connect your telegramApi credentials in Telegram Message Trigger.
  3. Configure Validate YouTube Link with two conditions: contains youtube. and contains youtu.be using {{ $json.message.text }}.
  4. Set the invalid-link path to Send Invalid Link Notice with Text set to not a youtube url and Chat ID set to {{ $('Telegram Message Trigger').item.json.message.chat.id }}.
  5. Credential Required: Connect your telegramApi credentials in Send Invalid Link Notice.
⚠️ Common Pitfall: If the link is shortened, ensure it matches youtu.be so Validate YouTube Link routes to processing.

Step 2: Connect YouTube Data Sources

Extract the video ID and trigger parallel API calls for transcript and metadata.

  1. Configure Dispatch Processing Note to send <i>Processing your input...</i> with Chat ID set to {{ $('Telegram Message Trigger').item.json.message.chat.id }}.
  2. Credential Required: Connect your telegramApi credentials in Dispatch Processing Note.
  3. In Assign Video Settings, set videoId to {{ $('Telegram Message Trigger').item.json.message.text.match(/youtu\.be\/([^?]+)/)[1] }} and languageCode to en.
  4. Assign Video Settings outputs to both Fetch Transcript via API and Retrieve Video Metadata in parallel.
  5. In Fetch Transcript via API, set URL to https://scraper-api.decodo.com/v2/scrape, Method to POST, and body parameters target: youtube_transcript, query: {{ $json.videoId }}, language_code: {{ $json.languageCode }}.
  6. Credential Required: Connect your httpHeaderAuth credentials in Fetch Transcript via API.
  7. In Retrieve Video Metadata, set URL to https://scraper-api.decodo.com/v2/scrape, Method to POST, and body parameters target: youtube_metadata, query: {{ $json.videoId }}.
  8. Credential Required: Connect your httpHeaderAuth credentials in Retrieve Video Metadata.
⚠️ Common Pitfall: The regex in Assign Video Settings assumes youtu.be format. Add a second extraction rule if you expect full youtube.com/watch URLs.

Step 3: Set Up Transcript Parsing and AI Summary

Transform transcript data into a single text block and generate a TLDR summary with Gemini.

  1. Leave the JavaScript in Derive Transcript Text as-is to output transcript, textArray, and totalSegments.
  2. Configure Create TLDR Summary with Text set to {{ $json.transcript }} and keep the prompt as defined.
  3. Gemini Flash Model is connected as the language model for Create TLDR Summary — ensure credentials are added to Gemini Flash Model, not the chain node.
  4. Credential Required: Connect your googlePalmApi credentials in Gemini Flash Model.

Step 4: Configure Summary Assembly and Parallel Outputs

Merge metadata and summary, then send the overview and format chunked messages in parallel.

  1. In Parse Video Details, keep the JavaScript intact to produce fields like title, duration, and summaryForAI.
  2. Configure Combine Summary Data with Mode set to combine and Combine By set to combineAll.
  3. Combine Summary Data outputs to both Send Video Overview and Format Summary Segments in parallel.
  4. In Send Video Overview, set Text to =📺 Youtube Video Analyze of **{{ $json.title }}** by **{{ $json.channel }}** ⏱️ Video Duration: {{ $json.duration }} {{ $json.summaryForAI.content }} Stats: {{ $json.summaryForAI.stats }} Chapters (if applicable) {{ $json.summaryForAI.structure }} and Chat ID to {{ $('Telegram Message Trigger').item.json.message.chat.id }}.
  5. Credential Required: Connect your telegramApi credentials in Send Video Overview.
  6. Keep Format Summary Segments JavaScript intact to split output into 4,000-character HTML chunks and include parseMode: 'HTML'.

Step 5: Configure Chunked Delivery and Throttling

Send each summary segment to Telegram with throttling to avoid rate limits.

  1. Connect Format Summary Segments to Iterate Message Chunks and ensure batching is enabled.
  2. In Send Summary Segment, set Text to {{ $json.text }} and Chat ID to {{ $('Telegram Message Trigger').item.json.message.chat.id }}.
  3. Credential Required: Connect your telegramApi credentials in Send Summary Segment.
  4. Set Throttle Delay to Amount 1 to add a one-second pause between messages.
  5. Wire Send Summary Segment → Throttle Delay → Iterate Message Chunks to loop through all chunks.
⚠️ Common Pitfall: Telegram limits message size; keep Format Summary Segments maxCharsPerChunk at 4000 to avoid failed sends.

Step 6: Add Error Handling

Capture workflow errors and send a formatted report to your admin channel.

  1. Use Error Event Trigger to listen for workflow errors.
  2. Keep the error formatting logic in Compose Error Report to generate a compact HTML message.
  3. In Notify Admin Channel, set Text to {{ $json.message }} and replace Chat ID [YOUR_ID] with your admin channel ID.
  4. Credential Required: Connect your telegramApi credentials in Notify Admin Channel.

Step 7: Test and Activate Your Workflow

Validate the full flow from Telegram input to summary delivery, then enable the workflow.

  1. Click Execute Workflow and send a YouTube link to your Telegram bot.
  2. Confirm you receive Dispatch Processing Note, then the Send Video Overview message and multiple Send Summary Segment chunks.
  3. Verify the parallel paths run: Combine Summary Data feeds both Send Video Overview and Format Summary Segments simultaneously.
  4. Trigger an error (e.g., invalid API key) and confirm Notify Admin Channel receives a formatted alert.
  5. Toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Telegram Bot API credentials can expire or be pasted wrong. If replies stop, check the bot token in your n8n Telegram credentials first, then confirm the bot is still active in BotFather.
  • If you’re using Wait nodes or external processing, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Decodo Scraper API 401/403 errors are usually a bad or expired key. Check the HTTP Header Auth credential (“Authorization”) and regenerate the key in the Decodo dashboard if needed.

Related Workflows

If your team also needs to ask follow-up questions after reading the TL;DW, YouTube to Telegram, summaries and Q&A on demand pairs well because it turns the same video into an interactive reference, not just a one-time summary.

For teams doing competitive research in a shared chat, YouTube to Telegram, instant summaries your team uses is a natural add-on since it’s built around making the output easier to collaborate on and reuse internally.

When the next step is turning insights into content, Telegram + Google Gemini: YouTube Shorts scripts fast helps you go from “good idea from a long video” to an actual script your editor can work with.

Need faster scanning with less fluff? YouTube to Telegram, skim friendly summaries on demand is worth adding when your goal is high volume intake and quick triage.

Finally, if you want to publish instead of just taking notes, Telegram + YouTube Shorts: publish-ready videos fast is the “distribution” counterpart to this workflow, turning a Telegram prompt into something ready to post.


Quick reference:

Frequently Asked Questions

How long does it take to set up this YouTube TL;DW automation?

About 30 minutes if you already have the API keys.

Do I need coding skills to automate YouTube TL;DW summaries?

No. You’ll mostly paste credentials and tweak a prompt.

Is n8n free to use for this YouTube TL;DW automation workflow?

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 Decodo and Google Gemini API usage costs.

Where can I host n8n to run this automation?

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.

Can I customize this YouTube TL;DW automation workflow for another language?

Yes, and it’s one of the easiest edits. Change the languageCode setting in the “Set: Video ID & Config” node so Decodo requests the right caption language. Then adjust the “Generate TLDR” prompt so Gemini formats headings and tone the way you want. Common tweaks include a more technical summary, a beginner-friendly version, or “tools-only” extraction for faster competitive research.

Why is my Telegram connection failing in this workflow?

Usually it’s a bad bot token or the wrong chat ID in the admin alert node. Regenerate the token in BotFather if you’re unsure, then update the Telegram credentials in n8n. If error alerts aren’t arriving, grab your user ID (many people use @userinfobot) and replace the value in the “Alert Admin” configuration. Also check that the bot is allowed to post in the chat where you’re testing, especially in groups.

How many videos can this YouTube TL;DW automation handle?

A lot, within reason. On n8n Cloud, the practical limit is your monthly executions and how many videos you process per day, while self-hosting has no execution cap (it depends on your server). The workflow itself processes one video per run, and most runs finish in under a couple minutes unless the transcript is huge or the APIs are slow. If you plan to do hundreds a day, add rate limiting and store results (Google Sheets is already in the workflow, so you’re close). Your main constraint will be API quotas and cost, not n8n logic.

Is this YouTube TL;DW automation better than using Zapier or Make?

Often, yes, because this flow benefits from parallel API calls, message chunking, and more detailed error handling than basic “trigger → action” automations. n8n also gives you a self-host option, which matters when you’re processing lots of videos. Zapier or Make can still work if you want something extremely simple and don’t care about transcript cleaning or structured outputs. If you’re torn, Talk to an automation expert and you’ll get a straight answer based on volume and workflow complexity.

Once it’s running, you stop treating YouTube like a time sink and start treating it like a searchable knowledge feed in Telegram. Honestly, that shift alone is worth the setup.

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.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.