YouTube Shorts + Telegram, daily videos without chaos

Posting Shorts “daily” sounds simple until you’re hunting for ideas, rewriting captions, waiting on renders, fixing vertical formatting, and then chasing approvals in five different places. It turns into busywork fast.

Marketing managers feel it when the calendar slips. Agency owners feel it when clients want more output but not more hours. And content leads stuck doing reviews in chat threads? Same mess. This YouTube Telegram automation gives you consistent daily publishing and a clean approval loop.

You’ll see how this n8n workflow goes from “scheduled run” to a finished YouTube Short, then pushes the final video into Telegram so review is quick, obvious, and centralized.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: YouTube Shorts + Telegram, daily videos without chaos

Click to explore

flowchart LR

    subgraph sg0["Scheduled Automation Flow"]
        direction LR
        n0@{ icon: "mdi:cog", form: "rounded", label: "Publish Video Upload", pos: "b", h: 48 }
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Trigger", pos: "b", h: 48 }
        n2@{ icon: "mdi:brain", form: "rounded", label: "Gemini Chat Engine", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "Structured Result Parser", pos: "b", h: 48 }
        n4["<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/perplexity.dark.svg' width='40' height='40' /></div><br/>Generate Video Concept"]
        n5@{ icon: "mdi:robot", form: "rounded", label: "Prompt & Copy Agent", pos: "b", h: 48 }
        n6["<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/>Initiate Video Render"]
        n7["<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/>Retrieve Render Status"]
        n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Render Completion Check", pos: "b", h: 48 }
        n9["<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 Rendered Video"]
        n10@{ icon: "mdi:cog", form: "rounded", label: "Save Video to Disk", pos: "b", h: 48 }
        n11@{ icon: "mdi:cog", form: "rounded", label: "Process Video Edit", pos: "b", h: 48 }
        n12@{ icon: "mdi:cog", form: "rounded", label: "Load Final Video", pos: "b", h: 48 }
        n13["<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/telegram.svg' width='40' height='40' /></div><br/>Dispatch Telegram Alert"]
        n14@{ icon: "mdi:swap-vertical", form: "rounded", label: "Assign Filenames & Topic", pos: "b", h: 48 }
        n15@{ icon: "mdi:cog", form: "rounded", label: "Delay for Rendering", pos: "b", h: 48 }
        n11 --> n12
        n4 --> n5
        n9 --> n10
        n1 --> n14
        n14 --> n4
        n7 --> n8
        n5 --> n6
        n12 --> n13
        n12 --> n0
        n10 --> n11
        n6 --> n15
        n2 -.-> n5
        n8 --> n9
        n8 --> n15
        n3 -.-> n5
        n15 --> 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 n1 trigger
    class n3,n5 ai
    class n2 aiModel
    class n8 decision
    class n6,n7,n9 api
    classDef customIcon fill:none,stroke:none
    class n4,n6,n7,n9,n13 customIcon

The Problem: Daily Shorts Become a Daily Fire Drill

Daily Shorts don’t usually fail because the team can’t create. They fail because the process is scattered. Ideas live in one place, scripts in another, renders happen somewhere else, and “final review” is a moving target that depends on who saw which message. Meanwhile, vertical formatting is its own little nightmare: wrong dimensions, blurry overlays, text that’s cut off on mobile, and that one clip that loops badly so retention tanks. After a week of that, consistency collapses. Honestly, it’s exhausting.

The friction compounds. Here’s where it breaks down in real life:

You spend about 1–2 hours a day just moving files, copying captions, and re-uploading versions.
Approvals get buried in Telegram threads, so “looks good” arrives after you already posted.
Vertical edits are inconsistent, which means the channel looks messy from one day to the next.
When rendering is slow or fails, there’s no reliable fallback and the schedule slips again.

The Solution: One Pipeline From Idea to YouTube + Telegram Review

This workflow turns daily Shorts into a repeatable system. It starts on a schedule (CRON), assigns filenames and a topic, then generates a short “video concept” using Perplexity. From that idea, an AI agent composes the full package in your voice: a tight Veo-3 prompt, plus a title, caption, description, tags, and hashtags that don’t sound like they were stitched together at the last minute. Next, n8n sends the render request to Kie.ai (Veo-3), waits, polls for completion, and downloads the finished clip. Then FFmpeg takes over to produce a platform-native 9:16 Short with clean text bands and a loop that feels intentional. Finally, the workflow uploads to YouTube Shorts and sends the final video to Telegram so review and approvals happen in one place.

The workflow begins with your schedule trigger, then moves through idea generation and copy creation. After the render is ready, it downloads, reformats to vertical, and publishes. Telegram receives the exact same final file your audience will see, so feedback is fast and specific.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Runs on a CRON schedule and assigns consistent filenames and topics.
Generates a short concept, then turns it into a full prompt and metadata package.
Submits a Veo-3 render request, waits, polls status, and downloads automatically.
Converts 16:9 to crisp 9:16 using FFmpeg with text bands for Shorts.

Cut “idea → published” from a few hours down to about 30 minutes of hands-off processing.
Daily output stays consistent even when the team is busy on campaigns.
Fewer formatting mistakes, because every clip goes through the same vertical pipeline.
Approvals become simple since the final video lands in Telegram automatically.
A repeatable creative pattern that makes the channel look intentional, not random.

Example: What This Looks Like

Say you publish one Short per day. Manually, you might spend 30 minutes on idea + prompt, another 30 minutes writing title/caption/hashtags, then about 20 minutes downloading, reformatting vertical, and uploading. That’s roughly 1.5–2 hours a day, and review still happens “somewhere in chat.” With this workflow, you set the schedule once and most days you only spend a few minutes checking the Telegram delivery and approving (or tweaking) the post.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
YouTube Data API v3 for uploading Shorts automatically
Telegram Bot API to send the final video for review
Kie.ai API key (request it from Kie.ai)
Perplexity API key (get it from your Perplexity account)
Google Gemini access for the chat/agent steps (via your Google AI setup)
FFmpeg installed to format video to 1080×1920

Skill level: Intermediate. You’ll connect a few APIs, set credentials in n8n, and confirm FFmpeg works on your machine or server.

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

How It Works

A scheduled trigger kicks it off. n8n runs on your chosen CRON schedule, assigns a topic and filenames, and starts the daily pipeline without anyone remembering to press a button.

The workflow generates the “creative brief” automatically. Perplexity creates a concise, surprising fact and angle, then an AI agent (Gemini/LLM) expands it into a Veo-3-ready prompt plus YouTube metadata you can actually reuse.

Rendering and status checks happen in the background. n8n sends the render request to Kie.ai, waits, polls for completion, and downloads the output only when it’s ready, which helps avoid broken runs and half-finished files.

FFmpeg formats the final Short and distribution happens. The workflow converts the video to 9:16 with clean overlays, uploads to YouTube Shorts, and sends the same final file to Telegram so approval is tied to the real deliverable.

You can easily modify the topic source (for example, swap Google Sheets in place of a static topic) to fit your content calendar. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Trigger

This workflow starts on a schedule, so first define when the automation should run.

Add and open Scheduled Automation Trigger.
Set the schedule options to your desired cadence (e.g., hourly, daily, or custom cron).
Connect Scheduled Automation Trigger to Assign Filenames & Topic.

Step 2: Connect the Concept Generation Service

Define the initial video topic and generate the concept using Perplexity.

Open Assign Filenames & Topic and set your fields for filenames or topic inputs as needed.
Connect Assign Filenames & Topic to Generate Video Concept.
Open Generate Video Concept and add your Perplexity settings for idea generation.
Credential Required: Connect your Perplexity credentials in Generate Video Concept.

Step 3: Set Up the AI Prompting Pipeline

Use the agent to generate prompts and copy based on the concept, with Gemini as the LLM and a structured parser for outputs.

Open Prompt & Copy Agent and configure the prompt logic for video scripts, titles, and descriptions.
Ensure Gemini Chat Engine is connected as the language model for Prompt & Copy Agent.
Ensure Structured Result Parser is connected to Prompt & Copy Agent as the output parser.
Credential Required: Connect your Google Gemini credentials in Gemini Chat Engine. The parser does not store credentials; add them to the parent node.

Step 4: Configure Rendering and Status Checks

Initiate rendering, wait for completion, and loop until the render is ready.

Open Initiate Video Render and configure the HTTP request to your rendering service.
Connect Initiate Video Render to Delay for Rendering.
Open Delay for Rendering and set the wait duration appropriate for your renderer.
Open Retrieve Render Status and configure the status check endpoint.
Use Render Completion Check to route completed renders to Fetch Rendered Video and incomplete renders back to Delay for Rendering.
Credential Required: Add authentication for the HTTP endpoints in Initiate Video Render, Retrieve Render Status, and Fetch Rendered Video if your API requires it.

Step 5: Save, Edit, and Load the Final Video

Once the rendered file is available, save it, run a command-line edit, and load the final output for distribution.

Configure Fetch Rendered Video to download the binary file.
Set Save Video to Disk to write the file to your chosen path.
Open Process Video Edit and add your command-line editing script (e.g., FFmpeg).
Configure Load Final Video to read the edited file for upload.

Step 6: Configure Output Actions

After the final file is loaded, the workflow notifies Telegram and publishes to YouTube simultaneously.

Ensure Load Final Video outputs to both Dispatch Telegram Alert and Publish Video Upload in parallel.
Open Dispatch Telegram Alert and configure the chat ID and message template.
Open Publish Video Upload and configure the upload parameters (title, description, tags, privacy).
Credential Required: Connect your Telegram credentials in Dispatch Telegram Alert.
Credential Required: Connect your YouTube credentials in Publish Video Upload.

Tip: Because Load Final Video triggers two branches, verify both outputs receive the correct binary property name and file path to avoid upload failures.

Step 7: Test and Activate Your Workflow

Run a full test to confirm rendering, editing, notifications, and publishing all succeed.

Click Execute Workflow to run from Scheduled Automation Trigger and monitor each node.
Confirm that Render Completion Check loops until it routes to Fetch Rendered Video.
Verify that Dispatch Telegram Alert posts a message and Publish Video Upload completes successfully.
Once successful, toggle the workflow to Active for production scheduling.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

YouTube OAuth credentials can expire or lose scope. If uploads fail, check your Google Cloud OAuth consent and the credential connection in n8n 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.
Kie.ai rendering can succeed but return a temporary URL that expires. If downloads fail, shorten the time between “render complete” and “fetch video,” or store the file immediately.

Frequently Asked Questions

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

About an hour if you already have the API keys and YouTube OAuth ready.

Do I need coding skills to automate YouTube Telegram automation?

No. You’ll mainly connect accounts, paste API keys, and adjust a few settings in n8n.

Is n8n free to use for this YouTube Telegram 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 Perplexity, Gemini, and Kie.ai (Veo-3) 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 Telegram automation workflow for a Google Sheets content calendar?

Yes, and it’s a common upgrade. Replace the “Assign Filenames & Topic” Set step with a Google Sheets lookup that pulls the next unused topic, then mark the row as published after “Publish Video Upload.” You can also branch the “Dispatch Telegram Alert” step to send to different Telegram chats based on channel or client. If you want multi-language, duplicate the “Prompt & Copy Agent” step and generate a second metadata package for the same rendered clip.

Why is my YouTube connection failing in this workflow?

Usually it’s OAuth scope or an expired token. Reconnect the YouTube account in n8n credentials, then confirm YouTube Data API v3 is enabled in the same Google Cloud project. If it still fails, check quota limits for uploads that day, because repeated tests can hit the cap faster than you’d expect.

How many videos can this YouTube Telegram automation automation handle?

If you self-host n8n, there’s no execution limit; it mostly depends on your server and how long renders take. On n8n Cloud, your plan sets monthly execution limits, and each run here can include multiple polling checks while waiting for the render. Practically, most teams run 1–5 videos per day without issues as long as Kie.ai and YouTube quotas are sized for it. If you plan to scale to dozens daily, add rate limiting and staggered CRON schedules.

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

For this workflow, n8n is usually the better fit because it handles multi-step logic (polling, waits, branching, file processing) without getting fragile or expensive. You also get a real self-hosting option, which matters when you’re generating and editing video files. Zapier and Make can still work for simple “notify me” flows, but end-to-end rendering plus FFmpeg formatting is where they tend to get awkward. If you’re on the fence, Talk to an automation expert and describe your volume and channels.

Set this up once and your “daily Shorts” goal stops being a daily scramble. The workflow handles the repeatable parts, and your team keeps control where it matters.

YouTube Shorts + Telegram, daily videos without chaos

How This Automation Works

n8n Workflow Template: YouTube Shorts + Telegram, daily videos without chaos

The Problem: Daily Shorts Become a Daily Fire Drill