🔓 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

Telegram + YouTube Shorts: publish-ready videos fast

Telegram + YouTube Shorts: publish-ready videos fast - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram + YouTube Shorts: publish-ready videos fast - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You have ideas. What you don’t have is the patience to turn each one into a Short with a script, clips, captions, hashtags, and a clean upload flow. That “quick video” becomes a whole production line.

This Telegram Shorts automation hits content marketers first, honestly. But agency owners and solo creators feel it too when daily posting turns into nightly editing.

You send a single Telegram message, approve the script, and the workflow generates four clips, merges them, stores everything in Google Drive, and can publish to YouTube for you. Below, you’ll see exactly how it runs and what to watch out for.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Telegram + YouTube Shorts: publish-ready videos fast

Why This Matters: Turning one idea into a finished Short

Creating Shorts “at scale” sounds fun until you try doing it for a week straight. You write a script, rewrite the hook, find or generate clips, download files, rename them, stitch scenes together, add captions, then do the YouTube metadata dance (title, description, hashtags). One small hiccup ruins the flow. A clip doesn’t match the script. A file goes missing. Or you forget which version was approved and upload the wrong one. It’s not one big task. It’s a pile of tiny ones that steals your best hours.

The friction compounds. Here’s where it usually breaks down.

  • You lose about 1–2 hours per video bouncing between writing, generating, downloading, and editing.
  • Quality gets inconsistent because you’re rushing the “boring parts,” like structure, pacing, and captions.
  • Assets end up scattered across laptops, chats, and random Drive folders, so reusing content becomes a hunt.
  • Publishing slips because you still need “one more step,” and that step keeps moving.

What You’ll Build: Telegram-to-YouTube Shorts content engine

This workflow turns one Telegram message into a publish-ready Short, with a human checkpoint where it matters. You start by messaging your Telegram bot with a topic. n8n picks it up, builds a clean prompt, and uses an AI chat model to write a four-part script plus a title, description, and hashtags. That script comes back to Telegram so you can approve it (or reject it) before anything expensive happens. Once approved, the workflow generates four cinematic clips with Gemini, uploads each clip to Google Drive, and keeps the URLs organized for the next step. Then it merges the clips via an external merge API, polls until the merge is complete, downloads the final video, and uploads the finished Short to Drive. Finally, you receive the final video link in Telegram and can optionally approve publishing straight to YouTube.

The workflow starts in Telegram, so your “content brief” is as easy as sending a message. AI handles the scripting and clip generation, then HTTP requests handle the merge and status checks. At the end, you get a Drive-stored final video and a one-tap decision to publish.

What You’re Building

Expected Results

Say you publish one Short per day. Manually, you might spend about 40 minutes writing and tightening the script, another 40 minutes generating/finding clips, then about 40 minutes merging, captioning, and getting it upload-ready. That’s roughly 2 hours a day. With this workflow, you send the topic in Telegram (1 minute), approve the script (maybe 5 minutes), then let generation and merging run in the background while you do other work. You’re mostly trading “hands-on hours” for “wait time.”

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram for the bot trigger and approvals
  • Google Drive to store clips and final videos
  • YouTube for optional auto-publishing
  • OpenAI API key (get it from the OpenAI dashboard)
  • Google Gemini access (enable it in Google AI Studio/Cloud)

Skill level: Intermediate. You’ll connect accounts, set credentials, and tweak a couple of prompts without touching code.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A Telegram message kicks things off. You send a topic to your bot, and n8n checks it’s a valid “start” style command before continuing.

The workflow builds a script you can approve. An AI agent assembles the prompt, the OpenAI chat node generates a structured response (script sections plus metadata), and Telegram sends it back asking you to confirm.

Four clips get generated and stored. After approval, Gemini generates Clip 1–4, each clip is uploaded to Google Drive, and the workflow keeps the URLs so it can stitch everything together reliably.

Clips are merged, delivered, and optionally published. n8n calls a merge endpoint via HTTP Request, polls until it’s done, uploads the final video to Drive, then sends you the finished link in Telegram. If you give permission, it downloads the final file and publishes to YouTube.

You can easily modify the approval steps to match your process, like requiring a second reviewer or routing approvals to a different Telegram chat. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Trigger

This workflow starts when a Telegram message is received and validated before processing begins.

  1. Add and open Incoming Telegram Trigger, then select updates for message.
  2. Credential Required: Connect your telegramApi credentials.
  3. In Start Command Check, set the condition Left Value to {{ $json.message.text }} and Right Value to /start.
  4. In Send Processing Notice, set Text to =Hey {{ $json.message.from.first_name }}! Your Request Is being processed. WARNING: DO not send an aditional message until full video is recived as it will interupt the process. and Chat ID to ={{ $('Incoming Telegram Trigger').item.json.message.chat.id }}.
  5. Credential Required: Connect your telegramApi credentials in Send Processing Notice.
If you want to allow other commands beyond /start, update the Start Command Check condition to include additional values.

Step 2: Connect Telegram Notifications & Approvals

Multiple Telegram nodes confirm the script, report clip status, and deliver the final video.

  1. In Request Script Confirmation, set Operation to sendAndWait and Response Type to freeText.
  2. Set Message to =HERE IS VIDEO SCRIPT: {{ $json.output.items[0].script }} Respond "CONFIRM" to proceed to video generation. and Chat ID to ={{ $('Incoming Telegram Trigger').item.json.message.chat.id }}.
  3. In Confirm Script Approval, confirm responses match Confirm, CONFIRM, or confrim using {{ $json.data.text }}.
  4. Configure Notify Clip One Ready, Notify Clip Two Ready, Notify Clip Three Ready, and Notify Clip Four Ready with Text values Video 1/4 generated through Video 4/4 generated and Chat ID set to ={{ $('Incoming Telegram Trigger').item.json.message.chat.id }}.
  5. In Deliver Final Video, set Operation to sendVideo, File to ={{ $json["Finished_Video"] }}, and Caption to ={{ $('Prompt Builder Agent').item.json.output.items[0].description }} {{ $('Prompt Builder Agent').item.json.output.items[0].hashtags }}.
  6. In Ask Social Post Permission, set Operation to sendAndWait with Response Type set to freeText and Message to =The video sends distorted but will post fine, telegram makes video fit a certain ratio, Would you like to post the video to your socials? Respond "POST" if so. .
  7. Credential Required: Connect your telegramApi credentials to all Telegram nodes (8 nodes handle notifications, approvals, and delivery).
⚠️ Common Pitfall: If Confirm Script Approval doesn’t match case variations, the clip generation branch won’t run.

Step 3: Set Up Prompt Builder Agent

The AI pipeline builds the script and prompts used to generate four video clips.

  1. Open Prompt Builder Agent and keep Prompt Type set to define.
  2. Ensure the prompt includes the user’s message with {{ $json.message.text }} and the JSON output schema shown in the node.
  3. Verify Structured Output Reader is connected as the output parser for Prompt Builder Agent; no credentials are required on the sub-node.
  4. Verify OpenAI Chat Engine is connected as the language model for Prompt Builder Agent and set to model gpt-5.1 with Timeout 3600000.
  5. Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
If the AI output fails to parse, confirm the schema in Structured Output Reader matches the JSON shape required by Prompt Builder Agent.

Step 4: Configure Clip Generation & Storage

After approval, four clips are generated in parallel, uploaded, and their URLs assigned for merging.

  1. Note that Confirm Script Approval outputs to Create Clip One, Create Clip Two, Delay Before Clip Three, and Create Clip Four in parallel.
  2. In Create Clip One, set Prompt to ={{ $('Prompt Builder Agent').item.json.output.items[0].prompt1 }} and keep Resource as video with aspect ratio 9:16.
  3. Repeat for Create Clip Two, Create Clip Three, and Create Clip Four with prompts prompt2, prompt3, and prompt4.
  4. In Delay Before Clip Three, set Unit to minutes and Amount to 1.5 before Create Clip Three runs.
  5. For Upload Clip One through Upload Clip Four, set Name to ={{$now.format('yyyyLLdd')}}{{ $json.fileName }} and choose the correct Drive folder (replace [YOUR_ID]).
  6. In Assign URL One, set the assignment name to prompt(1) with value ={{ $json.webContentLink }}. Repeat similarly in Assign URL Two (Prompt(2)), Assign URL Three (Prompt(3)), and Assign URL Four (Prompt(4)).
  7. Credential Required: Connect your googlePalmApi credentials to all Google Gemini nodes (6 nodes generate/download video).
  8. Credential Required: Connect your googleDriveOAuth2Api credentials to all Google Drive nodes (5 nodes upload clips and the merged video).
⚠️ Common Pitfall: Mismatched field names like prompt(1) vs Prompt(2) can break the merge step—use the exact assignment names shown above.

Step 5: Configure Clip Merging & Final Delivery

The four clip URLs are combined, merged via an API, polled for completion, then delivered.

  1. In Combine Clips, set Mode to combine, Combine By to combineByPosition, and Number Inputs to 4.
  2. In Merge API Call, set URL to https://queue.fal.run/fal-ai/ffmpeg-api/merge-videos, Method to POST, and JSON Body to the provided array mapping {{ $json["prompt(1)"] }}, {{ $json["Prompt(2)"] }}, {{ $json['Prompt(3)'] }}, and {{ $json['Prompt(4)'] }}.
  3. Set Header Parameters in Merge API Call and Check Merge Status to include Authorization: Key [CONFIGURE_YOUR_API_KEY] and Content-Type: application/json.
  4. In Check Merge Status, set URL to ={{ $json.status_url }}, then in Merge Complete Check ensure Status equals COMPLETED.
  5. In Delay Status Poll, set Amount to 30 to re-check status.
  6. In Fetch Merge Result, set URL to ={{ $json.response_url }}, then in Download Merged Video set URL to ={{ $json.video.url }} with Operation download.
  7. In Upload Merged Clip, use ={{$now.format('yyyyLLdd')}}{{ $json.fileName }} and in Assign Final URL set Finished_Video to ={{ $json.webContentLink }}.
  8. Assign Final URL outputs to Deliver Final Video, then to Ask Social Post Permission for optional publishing.
⚠️ Common Pitfall: The merge API requires a valid key—replace [CONFIGURE_YOUR_API_KEY] before testing.

Step 6: Configure Social Publishing

If the user approves posting, the merged video is downloaded and uploaded to YouTube Shorts.

  1. In Post Approval Check, confirm it matches POST, post, or Post using {{ $json.data.text }}.
  2. In Download For Publishing, set URL to ={{ $('Assign Final URL').item.json.Finished_Video }} and Operation to download.
  3. In Publish to YouTube, set Title to ={{ $('Prompt Builder Agent').item.json.output.items[0].title } #shorts, Description to ={{ $('Prompt Builder Agent').item.json.output.items[0].description }} #shorts {{ $('Prompt Builder Agent').item.json.output.items[0].hashtags }}, and Region Code to US.
  4. Credential Required: Connect your YouTube credentials in Publish to YouTube (this node has no credentials configured).
Publish to YouTube is disabled in the workflow; enable it when you’re ready to post automatically.

Step 7: Test and Activate Your Workflow

Validate each branch and make sure credentials and API keys are set before going live.

  1. Use Execute Workflow and send /start to your bot to trigger Incoming Telegram Trigger.
  2. Confirm that Send Processing Notice posts the status message and Request Script Confirmation delivers a script.
  3. Reply CONFIRM to trigger the parallel clip generation; verify each clip uploads and the “Video x/4 generated” messages appear.
  4. Check that the merge loop completes (status COMPLETED) and Deliver Final Video sends the merged file with caption.
  5. Respond POST to test Download For Publishing and Publish to YouTube (enable the node first).
  6. When successful, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • Telegram bot credentials can be fine, but the bot still won’t trigger if privacy settings or group permissions are wrong. Check BotFather settings and the chat permissions first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Google Drive uploads can fail silently when the selected folder ID is wrong or the connected Google account lacks access. Open the Drive node, re-pick the folder, and reauthorize if needed.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Next Steps

If your team also needs stronger scripts before you generate any video, Telegram + Google Gemini: YouTube Shorts scripts fast pairs nicely as a “script-first” companion so you can test angles and hooks quickly.

For teams doing both production and distribution, YouTube Shorts + Telegram, publish content on repeat is useful when you want a tighter publishing loop and recurring posting habits.

When you mainly want the files organized and delivered (but prefer manual uploads), Telegram to Google Drive, shorts delivered ready to post keeps the same “Telegram in, assets out” feel with less emphasis on auto-publishing.

Need a lighter workflow just for writing? Gemini + Google Docs: scripts drafted from one topic is great if your approval process lives in Docs comments and you want collaborators involved.

Finally, if you want to separate creation from publishing completely, Google Drive to YouTube, publish videos with less busywork lets you treat Drive as the handoff point, which is cleaner for teams.


Quick reference:

Quick Answers

What’s the setup time for this Telegram Shorts automation?

About 30–60 minutes if your Telegram, Google, and YouTube accounts are ready.

Is coding required for this Telegram Shorts automation?

No. You’ll connect accounts, paste API keys, and adjust a couple of prompts.

Is n8n free to use for this Telegram Shorts 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 OpenAI and Gemini usage, which is usually a few cents per run unless you generate lots of video.

Where can I host n8n to run this Telegram Shorts 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 modify this Telegram Shorts automation workflow for different use cases?

Yes, pretty easily. You can change the “Request Script Confirmation” Telegram step to route approvals to a client, a teammate, or even an internal channel. Swap the “Publish to YouTube” node for a different destination if you want Instagram Reels or TikTok instead (keep the same approval gate). And if you want a different style of video, update the prompt used by the AI agent so the four-part script and clip instructions match your format.

Why is my Telegram connection failing in this workflow?

Usually it’s a bot token issue or the bot isn’t allowed to read messages in that chat. Regenerate the token in BotFather, update it in n8n, and confirm the bot is added correctly (especially for groups). If it triggers sometimes but not always, check the “Start Command Check” logic because the workflow may ignore messages that don’t match the expected command format.

What volume can this Telegram Shorts automation workflow process?

On n8n Cloud Starter, you can typically run thousands of executions per month, and self-hosting removes execution caps (your server becomes the limit). In practice, the slow part is video generation and merging, so you’ll scale by running multiple workflows in parallel or spacing runs with Wait nodes. If you plan to generate several Shorts per hour, watch API rate limits and Drive storage.

Is this Telegram Shorts automation better than using Zapier or Make?

Often, yes. This workflow has branching approvals, polling for merge completion, and multi-step file handling, which is where Zapier and Make can get expensive or awkward. n8n also gives you a self-hosted option, which matters if you’re generating lots of content. The tradeoff is setup: you’ll do a bit more credential wiring up front. If your version is just “send me a script in Telegram,” a simpler tool may be enough. Talk to an automation expert if you want help choosing.

Set this up once and you stop rebuilding the same Short pipeline every day. The workflow handles the repeatable work so you can focus on ideas, angles, and what to post next.

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.