🔓 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 to YouTube, Shorts approved and published

Telegram to YouTube, Shorts approved and published - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram to YouTube, Shorts approved and published - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You sit down to “just make one Short,” and suddenly you’re juggling script ideas, voiceover tools, image generators, a video editor, and YouTube metadata. The worst part is the context switching. It makes simple content feel heavy.

This Telegram YouTube automation hits social media managers first, because consistency is their job. But digital marketers chasing growth and founders posting between meetings feel it too. The outcome is simple: a repeatable way to ship polished Shorts with fewer revisions, while still keeping control at two approval points.

You’ll see how the workflow turns a Telegram prompt into a generated concept, a full Short, and a published YouTube upload with ready-to-use title and description.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram to YouTube, Shorts approved and published

The Problem: YouTube Shorts Take Too Many Tools (and Too Many Revisions)

Publishing YouTube Shorts consistently sounds easy until you try to do it with quality. You need an idea that’s actually clickable, a script that fits the format, a voiceover that doesn’t sound robotic, visuals that match the story, and editing that keeps retention high. Then you still have to upload, title, describe, and tag it in a way that makes sense. Do this a few times and you’ll notice the real cost: hours lost to small decisions, plus rework when the output isn’t quite on-brand.

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

  • One Short can require 6–8 separate “mini tasks,” and each one comes with another tool login and another handoff.
  • When there’s no approval checkpoint, you end up fixing bad scripts and mismatched visuals after the whole video is already assembled.
  • Metadata gets rushed, so titles and descriptions drift away from what you actually want YouTube to rank and recommend.
  • Manual production makes “daily Shorts” feel impossible, which means you post less and growth slows down.

The Solution: Telegram-Driven Shorts Creation With Two Approvals

This workflow turns Shorts production into a guided pipeline that starts in Telegram and ends with a published YouTube Short. You send a prompt (or idea) to your Telegram bot, and the workflow generates a stronger concept, plus SEO-friendly title and description using OpenAI. You approve that idea first, which prevents wasted rendering. After approval, the workflow creates the script, generates a natural voiceover with ElevenLabs, builds images and animated clips via Replicate, and stores assets in Cloudinary. Then it assembles everything into a finished Short through Creatomate, asks for a final thumbs-up in Telegram, and only then publishes to YouTube with the metadata already prepared.

The workflow starts with a Telegram message and validates it so you don’t kick off a run with missing info. From there, AI creates the concept and script, media generation runs in the background (with wait steps), and the final video is rendered and delivered for approval before upload.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you publish 5 Shorts a week. Manually, you might spend about 20 minutes on ideation and metadata, 30 minutes generating voice and assets, and another hour assembling and fixing timing, which is roughly 2 hours per Short. With this workflow, you send the prompt in Telegram (a minute), approve the concept, wait for generation and rendering (often about 30–60 minutes total), then do a quick final approval. Your “hands-on time” drops to a few minutes per video.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram to submit prompts and approve steps.
  • OpenAI for ideas, scripts, and metadata.
  • ElevenLabs API key (get it from your ElevenLabs dashboard).
  • Replicate API key (get it from your Replicate account settings).
  • Cloudinary for storing voice and media assets.
  • Creatomate API key (get it from your Creatomate project settings).
  • 0CodeKit API key (get it from your 0CodeKit account).
  • YouTube channel with API access to publish automatically.

Skill level: Intermediate. You’ll paste API keys, connect Telegram and YouTube, and test a run end-to-end.

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

How It Works

Telegram kicks it off. You send a message to your bot, and the workflow checks that it’s usable (and that your keys are present) before it spends money generating assets.

The concept gets tightened up. OpenAI generates a stronger idea plus a title and description, and you approve that idea in Telegram. If you reject it, the workflow routes you into an “idea discussion” loop so you can refine the direction instead of starting over.

Media is produced in batches. The script is prepared, ElevenLabs generates the voiceover, Cloudinary stores the audio, and Replicate is used to generate images and video clips. Wait steps are included so n8n doesn’t try to fetch results before they exist.

The Short is assembled and published. Creatomate renders the final video, Telegram asks for the last approval, and the workflow converts the video into the right format and uploads it to YouTube. Once it’s live, you get an upload notice back in Telegram.

You can easily modify the prompt style to match your brand voice based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Trigger

This workflow begins when a user sends a message to Telegram, so the trigger must be connected and validated before anything else runs.

  1. Add and open Telegram Incoming Trigger.
  2. Connect your Telegram bot so incoming messages are captured by the trigger.
  3. Connect Telegram Incoming Trigger to Validate User Message to start the approval flow.

⚠️ Common Pitfall: All Telegram nodes require a bot credential. Add the same Telegram credentials to Telegram Incoming Trigger, Telegram Idea Approval, Telegram Reply Message, Telegram Processing Notice, Telegram Keys Missing, Telegram Final Approval, Telegram Video Rejected, and Telegram Upload Notice.

Step 2: Set Up User Validation and Idea Discussion

This step checks the incoming message and routes the conversation to the idea discussion agent and approval logic.

  1. Open Validate User Message and set your conditions for acceptable input.
  2. Confirm the path from Validate User Message to Idea Discussion Agent 💡 is connected.
  3. Ensure Idea Discussion Agent 💡 connects to Check Missing Idea, which then routes to Telegram Reply Message or Telegram Idea Approval.
  4. Review Idea Rejected so it passes back into Idea Discussion Agent 💡 when ideas are rejected.

OpenAI Chat Engine is connected as the language model for Idea Discussion Agent 💡 — ensure credentials are added to OpenAI Chat Engine, not to Format Model Output or Maintain Chat Memory.

Step 3: Configure API Key Validation and Input Variables

This section verifies required API keys and sets up the initial variables used by the AI generation pipeline.

  1. Open Telegram Processing Notice to confirm it informs the user that processing has started.
  2. In Configure API Keys, define any environment values or key placeholders needed by downstream HTTP requests.
  3. In Verify API Keys, set conditions that determine whether to continue to Define Input Variables or branch to Telegram Keys Missing.
  4. Connect Telegram Keys Missing to Stop Missing Keys to halt the workflow when credentials are missing.

⚠️ Common Pitfall: If Verify API Keys is too strict or too permissive, the workflow can halt unexpectedly or proceed without required tokens.

Step 4: Set Up AI Idea and Script Generation

The AI pipeline generates a video idea and converts it into a script.

  1. In Define Input Variables, add any fields that the AI prompt expects (topic, style, length, or target platform).
  2. Open Idea Generator 🧠 and configure the prompt for generating video concepts.
  3. Confirm that Idea Generator 🧠 connects into Prepare Script and then to Script to Audio Convert.
  4. Use Prepare Script to format or standardize the AI output before audio conversion.

⚠️ Common Pitfall: Idea Generator 🧠 and Image Prompt Builder 📷 are OpenAI nodes and require OpenAI credentials even though none are configured in the workflow.

Step 5: Configure Script Segmentation, Image Prompts, and Audio Upload

This step splits the script into segments, creates image prompts, and uploads audio for later assembly.

  1. Set up Script to Audio Convert to convert the script into audio via HTTP.
  2. Note that Script to Audio Convert outputs to both Segment Script Text and Cloudinary Upload in parallel.
  3. Use Segment Script Text and Separate Items to split the script into timed chunks.
  4. Configure Image Prompt Builder 📷 to turn segments into image prompts.
  5. Image Prompt Builder 📷 outputs to both Aggregate Prompt List and Request Image Batch in parallel.
  6. Configure Cloudinary Upload to store the generated audio file.

Step 6: Build Image and Video Batches

After prompts are prepared, the workflow requests images and video segments, waits for processing, and aggregates results.

  1. Configure Request Image Batch to send image prompts to your image generation API.
  2. Set Wait for Image Build to pause until images are ready, then proceed to Retrieve Images.
  3. Use Request Video Batch and Wait for Video Build to generate video clips from retrieved images.
  4. Confirm Retrieve Videos passes results into Aggregate Video List for combining.

With 10+ httpRequest nodes, keep a consistent base URL and authentication method across all API calls to simplify maintenance.

Step 7: Assemble Render and Approval Workflow

This section merges audio and video assets, creates the render payload, and requests final approval.

  1. Use Merge Video Audio to combine Aggregate Video List and Cloudinary Upload outputs.
  2. Send the merged data to Create Render JSON and then to Assign JSON Data.
  3. Dispatch the render request with Dispatch to Creatomate, then wait via Wait for Final Render.
  4. When complete, Fetch Final Video and pass data into Combine Video Variables, then send a decision message via Telegram Final Approval.
  5. Ensure Check Final Approval routes to Video to Base64 Encode for approvals and to Telegram Video Rejected for rejections.

Step 8: Upload and Publish to YouTube

This step converts the final video into a file and publishes it on YouTube, then notifies the user in Telegram.

  1. Configure Video to Base64 Encode to fetch or convert the final video for file decoding.
  2. Use Decode Base64 File to create a binary file usable by Publish to YouTube.
  3. Set up Publish to YouTube with your channel details and metadata.
  4. Ensure Telegram Upload Notice confirms successful upload to the user.

⚠️ Common Pitfall: Publish to YouTube requires YouTube OAuth credentials. Add them before testing uploads.

Step 9: Add Error Handling

The workflow includes error handling for missing API keys to prevent incomplete runs.

  1. Verify Verify API Keys routes missing keys to Telegram Keys Missing.
  2. Confirm Telegram Keys Missing connects to Stop Missing Keys to stop execution cleanly.

Step 10: Test & Activate Your Workflow

Run a full test to ensure the idea generation, approval flow, and final publishing pipeline are working end-to-end.

  1. In n8n, click Execute Workflow and send a Telegram message to trigger Telegram Incoming Trigger.
  2. Verify that the idea approval path reaches Telegram Idea Approval and proceeds to Telegram Processing Notice after approval.
  3. Confirm that a final approval message appears from Telegram Final Approval and that a publish occurs via Publish to YouTube.
  4. Check for a success confirmation from Telegram Upload Notice.
  5. When testing is complete, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • YouTube credentials can expire or need specific permissions. If things break, check your Google Cloud OAuth consent screen and the YouTube Data API access in your Google project 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.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Related Workflows

If your team also needs a simpler pipeline that still ends with upload-ready assets, OpenAI + YouTube Shorts, ready to upload videos is a good companion for testing formats before you add approvals and publishing.

For teams doing voice-led Shorts where speed matters more than fancy visuals, YouTube Shorts with OpenAI + ElevenLabs, ready fast pairs well because it focuses on script-to-voice output you can reuse across channels.

When you’re ready to distribute beyond YouTube, OpenAI + Blotato, YouTube Shorts on autopilot helps you push the same content to multiple platforms without doing extra uploads.

Need a more “daily posting” system that starts the same way (Telegram) but emphasizes consistency over review gates? YouTube Shorts + Telegram: post faceless videos daily is the next workflow many creators stack with this one.

Finally, if you want reporting and a lightweight content log, ElevenLabs to Google Sheets, promo videos tracked is handy for tracking what was produced, which voice was used, and what shipped this week.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Telegram YouTube automation automation?

About 15 minutes if your accounts and API keys are ready.

Do I need coding skills to automate Telegram YouTube automation?

No. You’ll connect services, paste API keys, and test approvals in Telegram.

Is n8n free to use for this Telegram YouTube 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, ElevenLabs, Replicate, Cloudinary, and Creatomate usage costs, which vary based on how many Shorts you generate.

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 Telegram YouTube automation workflow for a different brand voice and visual style?

Yes, and you should. Update the OpenAI prompts in the idea generation and image prompt steps (the OpenAI “Idea Generator” and “Image Prompt Builder” parts of the workflow) so they include your tone, banned phrases, and formatting rules. Many teams also swap the Replicate model choice to match their look, then adjust the Creatomate render JSON so captions and pacing fit their channel.

Why is my Telegram connection failing in this workflow?

Usually it’s the bot token, chat ID permissions, or the workflow listening for the wrong update type. Recheck the Telegram credentials in n8n, then confirm the bot is actually in the chat you’re messaging and allowed to post replies. If the trigger fires but approvals don’t, it’s often a mismatched chat/thread or a changed bot privacy setting.

How many videos can this Telegram YouTube automation automation handle?

A lot, but rendering and API quotas will be your real limits.

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

For this use case, yes, but it depends on how far you want to take it. This workflow needs branching logic (idea approved vs rejected, final approved vs rejected), waiting for external renders, and multi-step data shaping, and n8n is simply more comfortable there. You also get the option to self-host, which is a big deal when you start running lots of executions. Zapier or Make can work for simpler “send prompt, get output” flows, but they get awkward when you add approvals, batching, and file handling. If you’re on the fence, Talk to an automation expert and you’ll get a straight recommendation.

Two approvals, one pipeline, and far fewer “ugh, I have to rebuild this” moments. Set it up once and let the workflow do the repetitive work while you focus on the ideas that actually move the channel.

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.