🔓 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 Google Drive, shorts delivered ready to post

Telegram to Google Drive, shorts delivered ready to post - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram to Google Drive, shorts delivered ready to post - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Short-form video “production” can turn into a weird pile of half-finished clips, missing files, and links that worked yesterday but not today. Then you waste another hour trying to rebuild what should’ve been one simple post.

This Telegram Drive shorts automation hits content marketers first, honestly. But agency owners and solo creators feel it too, especially when you’re trying to post consistently without hiring an editor.

You send one prompt in Telegram. The workflow generates a visually consistent one-minute short, saves assets to Google Drive, merges everything, and delivers the final video back to you, ready to post.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram to Google Drive, shorts delivered ready to post

The Problem: Short-Form Video Gets Stuck in “Almost Done”

The annoying part about short-form video isn’t coming up with ideas. It’s everything that happens after. You generate a clip, download it, rename it, upload it somewhere, then you realize you need six more clips that match the same look. Now you’re juggling links, folders, and “final_final_v7.mp4” files. Miss one upload or paste the wrong URL and your merge tool can’t fetch the assets, so you start over. That’s not creative work. It’s friction dressed up as productivity.

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

  • You end up babysitting multiple clip generations just to keep the visuals consistent across scenes.
  • Saving and sharing files becomes a mini project, and one broken link can kill the whole merge.
  • Without a simple log, you can’t track which prompts produced which videos, so repeating what worked is hard.
  • Manual stitching and re-uploading steals the time you planned to use for writing hooks and testing new angles.

The Solution: One Telegram Prompt In, One Ready-to-Post Short Out

This n8n workflow turns Telegram into your “start button” for a full short-form production pipeline. You message your bot with a trigger command (like /makevideo plus your topic). An AI agent reformats that idea into a structured plan, then generates a sequence of video clips (seven scenes) designed to feel coherent, not random. As each clip is created, it’s uploaded into a designated Google Drive folder and turned into a shareable URL so a merging service can reliably fetch it. When all clips are ready, the workflow sends an API request to merge them into a single one-minute video, checks status until it’s complete, then delivers the finished video back to you in Telegram.

The workflow starts with a Telegram message and a quick confirmation step. Then it creates and stores each clip in Google Drive, collects the URLs, and calls a merge API (with automatic re-checks). Finally, you receive the final one-minute short in Telegram, plus your Drive folder stays organized for reuse.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you publish 5 shorts a week and each one needs 7 scenes. Manually, that often looks like generating 7 clips, downloading 7 files, uploading 7 files to storage, then copying 7 links into a merger, which is easily about 10 minutes per clip once you count the little fixes (so roughly 70 minutes per short). With this workflow, you spend about 2 minutes sending the Telegram prompt and confirming, then you wait while clips generate and merge in the background. You get the final video in Telegram, and all assets are already in Google Drive.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram to send prompts and receive videos.
  • Google Drive to store clips and final exports.
  • Google Sheets for logging prompts and runs.
  • OpenAI API key (get it from your OpenAI API dashboard).
  • Google (Gemini/Veo) access for generating the video clips.
  • Merge API access (FAL) (get it from your FAL account settings).

Skill level: Intermediate. You’ll connect accounts, paste a few API keys, and test one 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 message triggers the run. You send a command like /makevideo plus a topic to your Telegram bot, and the workflow replies immediately so you know it started.

Your prompt gets “production-ready.” An AI agent (OpenAI chat + a structured parser) turns the idea into consistent scene instructions, then logs the request into Google Sheets for tracking and reuse.

Clips are generated and stored as they finish. The workflow creates seven video clips (Veo/Gemini), uploads each one to Google Drive, and records a public URL for merging. You also get progress updates in Telegram as clips become ready.

Everything merges into one final short. n8n sends the clip URLs to a merge API via HTTP request, checks status with a simple loop and waits, then fetches the final video and sends it back to you in Telegram.

You can easily modify the number of clips to match your style (for example, 5 scenes instead of 7) 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 starts when a user sends a message to Telegram. You’ll wire the trigger and the immediate notification branch.

  1. Add and configure Telegram Intake Trigger to listen for updates set to message.
  2. Credential Required: Connect your Telegram credentials in Telegram Intake Trigger (this workflow does not include credentials).
  3. In Telegram Start Notice, set Chat ID to ={{ $('Telegram Intake Trigger').item.json.message.chat.id }} and 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..
  4. Confirm the parallel start: Telegram Intake Trigger outputs to both Telegram Start Notice and Prompt Composer Agent in parallel.

⚠️ Common Pitfall: If Telegram credentials are missing, the trigger will never fire and notifications will fail. Add Telegram credentials to all Telegram nodes (10+ notification nodes in this workflow).

Step 2: Connect Google Sheets

The AI script and prompts are stored in a sheet before video generation begins.

  1. Open Append to Sheets and set Operation to appendOrUpdate.
  2. Set Document to [YOUR_ID] (named VEO Videos) and Sheet Name to Sheet1 (value gid=0).
  3. Map columns exactly as shown, for example Script to ={{ $('Prompt Composer Agent').item.json.output.items[0].script }} and Prompt 1 to ={{ $('Prompt Composer Agent').item.json.output.items[0].prompt1 }} through Prompt 7.
  4. Credential Required: Connect your Google Sheets credentials in Append to Sheets (this workflow does not include credentials).

Step 3: Set Up Prompt Composer Agent (AI Orchestration)

This step builds the structured script and seven prompts using an AI agent and a structured output parser.

  1. In Prompt Composer Agent, keep the long prompt block and ensure the Prompt Type is define with Has Output Parser enabled.
  2. Ensure OpenAI Chat Engine is connected as the language model for Prompt Composer Agent. Credential Required: Connect your OpenAI credentials in OpenAI Chat Engine (the agent uses these credentials).
  3. Ensure Structured JSON Parser is connected as the output parser for Prompt Composer Agent. Credential Required: Add any AI-related credentials to Prompt Composer Agent (not the parser sub-node).
  4. Confirm the flow: Prompt Composer Agent → Append to Sheets → Request Confirmation.

Tip: Request Confirmation uses sendAndWait and expects a free-text reply. Keep the message text as shown: LOOK AT THE MOST RECENT SPREADHSEET INPUT AND THEN REPLY WITH: "CONFIRM" OR "RETRY".

Step 4: Configure Video Generation, Storage, and Notifications

Seven clips are generated via Gemini, stored in Drive, and each completion sends a Telegram update. Several nodes run in parallel.

  1. For each Gemini node (Create Clip One through Create Clip Seven), set Prompt to the appropriate sheet field, e.g. Create Clip One uses ={{ $('Append to Sheets').item.json['Prompt 1'] }}.
  2. Confirm waiting buffers: Delay Before Clip Three, Delay Before Clip Five, and Delay Before Clip Seven each set Unit to minutes and Amount to 1.5.
  3. In each Drive storage node (Store Clip One through Store Clip Seven), set Name to ={{$now.format('yyyyLLdd')}}{{ $json.fileName }} and select the Folder [YOUR_ID] (cached name VEO VIDEOS).
  4. In each Set node (Mark URL One through Mark URL Seven), map the output URL. Example: Mark URL One assigns prompt(1) to ={{ $json.webContentLink }}.
  5. Confirm parallel branching: Create Clip One outputs to both Store Clip One and Notify Clip One Ready in parallel (repeat this pattern for Clips Two–Seven; Create Clip Seven also triggers Notify All Clips Ready).
  6. Credential Required: Connect your Google Gemini credentials to all Create Clip One–Create Clip Seven nodes (7 nodes).
  7. Credential Required: Connect your Google Drive credentials to all Store Clip One–Store Clip Seven nodes (7 nodes).
  8. Credential Required: Connect your Telegram credentials to all notification nodes (Notify Clip One Ready through Notify All Clips Ready).

⚠️ Common Pitfall: The URL fields are case-sensitive. Mark URL One uses prompt(1) while others use Prompt(2), Prompt(3), etc. This must match the JSON body in Merge API Call.

Step 5: Configure Merge and Polling Logic

Once all URLs are gathered, clips are merged via an HTTP API, then polled until completed.

  1. In Combine Clip URLs, set Mode to combine, Combine By to combineByPosition, and Number Inputs to 7.
  2. In Merge API Call, keep URL as https://queue.fal.run/fal-ai/ffmpeg-api/merge-videos and set Method to POST with Specify Body set to json.
  3. Set JSON Body to the provided expression block, ensuring the seven URL references match: ={{ $json["prompt(1)"] }}, ={{ $json["Prompt(2)"] }}, ={{ $json['Prompt(3)'] }}, ={{ $json['Prompt(4)'] }}, ={{ $json['Prompt(5)'] }}, ={{ $json['Prompt(6)'] }}, ={{ $json['Prompt(7)'] }}.
  4. Set headers in Merge API Call and Check Merge Status to include Authorization Key [CONFIGURE_YOUR_API_KEY] and Content-Type application/json.
  5. In Check Merge Status, set URL to ={{ $json.status_url }}.
  6. In Merge Complete?, keep the condition Left Value ={{ $json.status }} equals COMPLETED.
  7. In Pause Before Recheck, set Amount to 30 seconds to throttle polling before looping back to Check Merge Status.

Step 6: Configure Output Delivery

When the merge is complete, the final video is fetched and delivered to the user in Telegram.

  1. In Fetch Merge Result, set URL to ={{ $json.response_url }} and include the same API headers as the merge request.
  2. In Send Final Video, set Operation to sendVideo, File to ={{ $json.video.url }}, and Chat ID to ={{ $('Telegram Intake Trigger').item.json.message.chat.id }}.
  3. Credential Required: Connect your Telegram credentials to Send Final Video if not already connected.

Step 7: Test and Activate Your Workflow

Validate the end-to-end flow from Telegram intake to final merged video delivery.

  1. Use Telegram Intake Trigger to send a test message and verify you receive Telegram Start Notice immediately.
  2. Confirm that Append to Sheets writes a new row with Script and Prompt 1–7 fields populated from Prompt Composer Agent.
  3. Reply to Request Confirmation with CONFIRM to proceed; verify that video creation begins and Telegram notifications arrive for clips 1–7.
  4. Check that Merge API Call runs after Combine Clip URLs and that Merge Complete? eventually routes to Fetch Merge Result.
  5. A successful run ends with Send Final Video delivering the merged video to Telegram.
  6. When satisfied, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Drive permissions matter. If the merge can’t fetch clips, check the sharing settings on the uploaded files and the target folder 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 you want the same “prompt to asset” experience but your bottleneck is publishing, Telegram + YouTube Shorts: publish-ready videos fast pairs nicely once Drive is acting as your clean source folder.

For teams that also need the packaging pieces (thumbnails plus short clips), Telegram + KIE.ai: thumbnails and clips in one chat helps you keep everything in a single conversation instead of bouncing between tools.

When you prefer delivery to an inbox for approvals or client review, Veo 3 to Gmail, daily short videos delivered is a clean add-on to your production workflow.

Need product-style shorts built from existing photos instead of text prompts? Telegram to Google Cloud, product videos from photos is the better fit for ecommerce and catalog-based content.

Finally, if you’re trying to scale experiments and measure what’s working, VietVid.com + Google Sheets: track every Veo3 render gives you tighter reporting around renders, prompts, and output consistency.


Quick reference:

Frequently Asked Questions

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

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

Do I need coding skills to automate Telegram Drive shorts?

No. You’ll mostly paste API keys and connect Telegram and Google Drive. The “logic” is already built into the workflow.

Is n8n free to use for this Telegram Drive shorts 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 video generation/merge API usage, which varies with how many shorts you generate.

Where can I host n8n to run this Telegram Drive 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 customize this Telegram Drive shorts workflow for 5 scenes instead of 7?

Yes, but you’ll want to do it carefully. The easiest approach is to remove the extra “Create Clip” + “Store Clip” + “Mark URL” nodes for the scenes you don’t need, then update the Merge step that combines clip URLs so it only expects five. Common customizations include changing the Drive folder, tweaking the prompt composer to match your brand voice, and adjusting wait times so the merge status check doesn’t fire too early.

Why is my Google Drive connection failing in this workflow?

Usually it’s expired Google credentials or missing Drive permissions on the account you connected. Reconnect Google Drive in n8n, confirm the target folder still exists, and verify files are being created where the workflow expects. Also check sharing settings, because the merge service needs URLs it can actually access.

How many videos can this Telegram Drive shorts automation handle?

On a typical n8n Cloud plan, it can handle plenty for a small team, and self-hosting removes execution limits (your server becomes the bottleneck).

Is this Telegram Drive shorts automation better than using Zapier or Make?

For AI-heavy, multi-step video workflows, n8n is usually a better fit because you can branch, retry, wait, and poll external APIs without turning every small step into a separate billable task. The workflow also benefits from having “state” across many nodes (seven clip URLs, merge status checks, retries), which is where simpler automation tools can get fragile. Zapier or Make can still work if you trim the scope down to something like “Telegram prompt → one clip → send link,” but you’ll lose the full studio-style pipeline. If you’re deciding between approaches, think about volume and how much you hate babysitting failures. Talk to an automation expert if you want help choosing.

Once this is running, “make a short” becomes a single message you send, not a mini editing session. The workflow handles the repetitive parts so you can focus on posting, iterating, and moving on.

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.