🔓 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, music videos delivered

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

You have a song idea. Then comes the mess: prompts, tools, waiting on renders, hunting down files, and trying to remember which version was “the good one.” It’s not hard work. It’s just too much glue work.

This Telegram Drive automation hits content creators first, but marketing managers and small agency teams feel it too. You want a clean handoff from “idea” to “deliverable,” without spending your evening babysitting exports.

This workflow turns a Telegram message (text or voice) into an AI-generated track, artwork, and a finished music video link in Google Drive, with every request tracked in Google Sheets. You’ll see what it automates, what results you can expect, and what you need to run it reliably.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram to Google Drive, music videos delivered

The Problem: Music Video Creation Turns Into Tool-Hopping

Making an AI music video sounds quick until you do it more than once. You collect the idea somewhere, generate lyrics somewhere else, kick off music generation, wait, download audio, upload it, then repeat the same dance for cover art and a looping background. Half the time, the “status check” is you refreshing a dashboard and hoping it finished. Meanwhile, requests pile up in DMs, and you lose track of which chat needs which file. One missed step and you’re re-rendering or re-uploading. Again.

It adds up fast. Here’s where it usually breaks down.

  • Song requests live in Telegram, but production notes live in your head, so follow-ups get missed.
  • Downloading and re-uploading audio, images, and video files can eat about 30 minutes per track.
  • Status polling (is it done yet?) becomes a constant interruption during the day.
  • Without a central log, you can’t confidently scale beyond a few requests a week.

The Solution: Telegram In, Finished Music Video Link Out

This n8n workflow turns Telegram into your “request inbox” for music video production. A user sends a song idea by text or voice, and the workflow captures it, cleans it up, and logs it to Google Sheets so the request is never floating around untracked. From there, AI agents generate lyrics and prompts, then API calls create the actual music, cover art, and a video background. When assets are ready, the workflow merges audio and video into a final clip (using a rendering service), uploads the deliverables to Google Drive, updates the same Google Sheet with links and status, and finally replies back in Telegram with the finished video link. Clean loop. No guessing who gets what.

The workflow starts with a Telegram trigger, then routes voice messages through transcription so everything becomes structured text. Next, Google Sheets acts like a lightweight production queue. Once generation and rendering finish, Google Drive becomes the single source of truth, and Telegram becomes the delivery channel.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you produce 5 custom tracks a week. Manually, even a “simple” run is often 6 steps: capture the idea, write or refine lyrics, generate music, generate art, generate a background clip, then merge and upload. If you spend about 10 minutes per step, that’s roughly 5 hours a week of hands-on busywork. With this workflow, you send the idea in Telegram (about 2 minutes), and the rest runs in the background until the Google Drive link comes back. You still review the result, but you stop doing the repetitive parts.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram Bot API to receive requests and reply.
  • Google Sheets to track requests and statuses.
  • Google Drive to store assets and final videos.
  • Creatomate to render the final audio + video.
  • AI API keys (from your providers’ dashboards) for music, images, and video generation.

Skill level: Beginner. You’ll connect accounts, paste API keys, and copy template IDs into the right fields.

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

How It Works

A Telegram message starts everything. A user sends a text prompt or a voice note. Voice messages get downloaded and transcribed so the workflow can treat both formats the same way.

The request gets logged and queued. The workflow writes a new row into Google Sheets (idea, metadata, chat ID), which doubles as a simple production tracker. Honestly, this is where most DIY setups fall apart, and this fixes it.

AI generation runs in stages. Agents generate lyrics and prompts, then HTTP requests kick off music generation and media generation. Wait steps and status checks keep it from racing ahead before files are ready.

Rendering and delivery happen automatically. Once audio and video assets are available, the render service creates the final clip, uploads it to Google Drive, updates the Sheet with the final URL, and sends that link back to the original Telegram chat.

You can easily modify the prompting and the render template to match your genre, pacing, and brand visuals. 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 Telegram message or voice note, routed through branching logic for text or audio input.

  1. Add and open Telegram Ideas Trigger and connect it to your Telegram bot setup. Credential Required: Connect your Telegram credentials.
  2. Open Route Text or Voice and define switch rules that route text to Assign Mode Text and voice to Download Voice Clip.
  3. Open Download Voice Clip and ensure it pulls the voice file from the incoming Telegram event. Credential Required: Connect your Telegram credentials.
  4. Open Transcribe Voice Clip and set your transcription model settings. Credential Required: Connect your OpenAI credentials.
  5. Confirm Transcribe Voice Clip flows to Assign Fields, which then outputs to Music AI Agent.

⚠️ Common Pitfall: The Telegram nodes have no credentials configured in the template. You must add your bot credentials or the trigger will not fire.

Step 2: Connect Google Sheets

Google Sheets drives track intake, pending rows, and status updates across multiple branches of the pipeline.

  1. Open Sheets Trigger Start Tracks and configure the spreadsheet and sheet tab it should monitor. Credential Required: Connect your Google Sheets credentials.
  2. Open Retrieve Pending Row and set it to fetch a row that represents a pending track. Credential Required: Connect your Google Sheets credentials.
  3. Open Update Audio URL in Sheet, Update Cover & Video URLs, and Update Video URL & Status to map output fields back to the correct row. Credential Required: Connect your Google Sheets credentials.
  4. For tool nodes Append Tracks to Sheets and Fetch Track Rows from Sheets, ensure Google Sheets credentials are connected in Music AI Agent (credentials are added to the parent agent, not the tool).

Tip: Because this workflow uses multiple Google Sheets nodes (triggers, reads, updates), use one shared credential to avoid access mismatches across branches.

Step 3: Set Up AI Agents and Language Models

Three agent nodes orchestrate lyrics, prompts, and music planning using OpenAI and Gemini language models plus tools.

  1. Open OpenAI Dialogue Model and OpenAI Dialogue Model B and connect OpenAI credentials. Credential Required: Connect your OpenAI credentials.
  2. Open Gemini Chat Engine and connect Google Gemini credentials. Credential Required: Connect your Google Gemini credentials.
  3. Verify OpenAI Dialogue Model is connected to Music AI Agent, and OpenAI Dialogue Model B is connected to Lyric Generation Agent.
  4. Ensure Basic Memory Buffer, Structured Output Reader, and Structured Output Reader B are connected as AI sub-nodes to their parent agents. Add any required credentials to the parent agent, not the sub-nodes.
  5. Connect SerpAPI Music Research as a tool for Music AI Agent and add SerpAPI credentials to Music AI Agent (not on the tool itself). Credential Required: Connect your SerpAPI credentials.

⚠️ Common Pitfall: AI tool sub-nodes like SerpAPI Music Research and Append Tracks to Sheets do not store credentials themselves—add credentials to Music AI Agent.

Step 4: Configure Media Generation and Status Polling

This section manages music creation, polling cycles, and the audio asset download pipeline.

  1. Open Lyric Generation Agent to confirm it outputs into Music Generation API Call.
  2. Configure Music Generation API Call with your music generation API endpoint and payload.
  3. Ensure the polling loop flows from Music Generation API Call → Pause Cycle → Check Generation Status → Verify Generation Status.
  4. Verify Verify Generation Status routes success to Download Audio File and retry cycles back through Pause Cycle and Rate Limit Pause.

Tip: The multiple wait nodes (including Pause Cycle and Rate Limit Pause) help avoid API throttling—keep these delays consistent with your API rate limits.

Step 5: Configure Cover Art and Video Generation (Parallel Branching)

Once audio is ready, the workflow generates cover art and a video stream in parallel.

  1. Open Cover & Video Prompt Agent and verify it receives inputs from Update Audio URL in Sheet.
  2. Cover & Video Prompt Agent outputs to both Generate Square Cover and Generate Wide Cover in parallel.
  3. Configure Generate Square Cover and Generate Wide Cover with your image generation endpoints.
  4. Ensure image retrieval and conversion flow: Generate Square Cover → Pause Step A → Fetch Image URL A → Retrieve Image Asset → Upload Square Cover Drive; and Generate Wide Cover → Pause Step B → Fetch Image URL B → Retrieve Image Asset B → Kraken Upload for URL → Convert Wide Cover to Video.
  5. Confirm video polling flow: Convert Wide Cover to Video → One Minute Delay → Check Video Status → Verify Video Status → Download Video File → Upload Video to Drive.

⚠️ Common Pitfall: The cover/video branch uses multiple HTTP endpoints; verify each httpRequest node has the correct URL and authentication headers for your image/video services.

Step 6: Configure Google Drive Uploads and Telegram Notifications

Final assets are stored in Drive, merged, and user notifications are sent via Telegram.

  1. Open Upload Audio to Drive, Upload Square Cover Drive, Upload Video to Drive, and Rename Drive Video and connect Google Drive credentials. Credential Required: Connect your Google Drive credentials.
  2. Ensure Upload Audio to Drive updates Update Audio URL in Sheet before the cover generation branch begins.
  3. Verify Upload Square Cover Drive and Upload Video to Drive merge in Combine Streams before updating Update Cover & Video URLs.
  4. Configure Send Telegram Status Update and Send Video Link to User to notify users. Credential Required: Connect your Telegram credentials.

Tip: Use consistent Drive folder IDs across all Google Drive nodes to keep audio, cover art, and video assets organized.

Step 7: Configure the Render Pipeline Trigger

A separate Sheets trigger handles the audio/video render pipeline for completed rows.

  1. Open Render Video Sheets Trigger and configure the spreadsheet and sheet to watch for render-ready entries. Credential Required: Connect your Google Sheets credentials.
  2. Configure Fetch Render Pending Row to select the correct pending row for rendering. Credential Required: Connect your Google Sheets credentials.
  3. Ensure the render flow connects Fetch Render Pending Row → Render Audio and Video → Pause Render Step → Send URL to Drive Script → Rename Drive Video → Update Video URL & Status → Send Video Link to User.

Step 8: Test and Activate Your Workflow

Validate each path manually before enabling the workflow for production.

  1. Click Execute Workflow and send a test message to Telegram Ideas Trigger (both text and voice) to validate branching and transcription.
  2. Confirm that Music Generation API Call starts, and that Download Audio File and Upload Audio to Drive produce a valid Drive file URL.
  3. Check that Cover & Video Prompt Agent splits into Generate Square Cover and Generate Wide Cover in parallel and eventually updates Update Cover & Video URLs.
  4. Verify Send Telegram Status Update and Send Video Link to User deliver messages with the final asset URLs.
  5. When everything succeeds, toggle the workflow to Active to enable continuous automation.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Drive credentials can expire or need specific permissions. If things break, check the n8n Credentials panel and the target Drive folder sharing settings 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 to publish finished videos (not just store them), Telegram to YouTube, playlist videos published faster is a natural next step once your Drive delivery flow is stable.

For teams doing production planning in spreadsheets, Google Sheets to YouTube, videos queued and published pairs well because the same tracking sheet can become your publishing queue.

When you want tighter control over templates and consistent edits, Google Sheets to Creatomate, shorts ready to post is useful alongside this workflow’s rendering approach.

Need a faster way to generate visuals for short clips without hunting stock footage manually? Pexels + Creatomate: YouTube Shorts made for you helps fill the “backgrounds and B-roll” gap for social cutdowns.

Finally, if you want to keep music outputs neatly organized by artist, vibe, or campaign, Telegram to Google Drive, organized Suno playlists complements this by turning Drive into a structured library instead of a dumping ground.


Quick reference:

Frequently Asked Questions

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

Plan on about an hour if you already have your API keys and templates.

Do I need coding skills to automate Telegram Drive automation?

No. You’ll mostly connect accounts, paste keys, and copy a few IDs into the right fields.

Is n8n free to use for this Telegram Drive 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 AI provider costs, like music generation credits ($5 gets you 1000 credits, and a song generation costs 12 credits) plus image/video generation (about $0.04 per image and about $0.16 per 10 seconds of video).

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 Drive automation workflow for generating two song versions and letting the user pick?

Yes, but you’ll want to make the choice visible in Google Sheets first. This workflow already generates two versions by default in the music generation step, so you can update the Google Sheets “append track” part to store both URLs, then tweak the Telegram message node to ask the user which version to render. If you’d rather keep it simple, change the music generation API call so it only creates one version per request.

Why is my Telegram connection failing in this workflow?

Usually it’s the bot token or webhook setup. Regenerate your Telegram bot token (or re-copy it) and update it in n8n Credentials, then confirm the bot can receive messages in the chat you’re testing. If voice messages fail but text works, check that the workflow has permission to download files and that the “download voice clip” node is receiving a valid file ID. Rate limits can also show up as random failures if you trigger a lot of generations at once.

How many requests can this Telegram Drive automation automation handle?

On n8n Cloud Starter, you’re limited by your monthly executions, so “a few hundred requests” is realistic if each request triggers lots of steps. If you self-host, there’s no execution cap, and the real limits become your server resources plus the AI providers’ rate limits. In practice, this workflow works best as a queued system: let Google Sheets triggers pick up pending rows and process them steadily, instead of trying to render everything instantly.

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

For a multi-stage pipeline like this, n8n is usually the better fit. You need branching, waiting, status checks, file handling, and a few different “loops” across Sheets triggers, and that gets expensive or awkward in Zapier-style task pricing. n8n also gives you the self-host option, which matters once you’re processing lots of requests. The tradeoff is setup: you’ll spend more time upfront connecting APIs and testing end-to-end. If you want someone to sanity-check your setup before you go live, Talk to an automation expert.

Once this is running, your process stops being a pile of tabs and half-finished exports. You send an idea, and you get a Drive link back.

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.