🔓 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

Google Drive to Telegram, instant team answers

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

Your team keeps asking the same questions, and you keep answering them. “Where’s the latest refund policy?” “What’s our day-off process?” “Which tools are approved?” It’s not hard work. It’s just relentless.

This is the kind of mess that hits Ops leads first, but support managers and founders feel it too. With Drive Telegram answers in place, you can turn your Google Drive docs into a Telegram assistant that replies in seconds using the most current policy text.

Below, you’ll see how the workflow stays updated when files change, how questions get answered (even from voice notes), and what you need to run it without babysitting it.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Drive to Telegram, instant team answers

The Problem: Team Knowledge Lives in Docs, Not in Chat

Google Drive is where policies go to “live,” which usually means they’re buried in folders, half-updated, and only findable by the one person who made them. Meanwhile, the actual work happens in Telegram. So the same questions bounce around every week, and someone has to stop what they’re doing to paste an answer (again). The worst part is confidence. If you’re not 100% sure you found the newest version, you hesitate, you caveat, and the thread drags on.

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

  • People ask in chat because searching Drive feels slower than pinging a coworker.
  • Answers drift over time, so two managers can give two “correct” policies.
  • Voice notes make it worse, because now someone has to listen, interpret, and type back.
  • When a policy doc changes, nobody has time to “retrain the team,” so confusion quietly returns.

The Solution: Google Drive Docs → Telegram Answers (Always Current)

This workflow turns a shared Google Drive folder into a living knowledge base that your team can query from Telegram. When someone sends a message to your Telegram bot, the workflow decides if it’s text or a voice note. Voice notes get transcribed, then treated like any other question. Next, the assistant searches a Supabase vector database (built from your Drive documents) to pull the most relevant passages. Finally, OpenAI generates a clear answer grounded in that pulled context and sends the reply back to Telegram, so your team gets a fast, consistent response instead of a long thread.

The other half is what makes it actually reliable. Two Drive-triggered automations watch for new files and file edits. When a doc changes, the workflow re-extracts the text, splits it into chunks, creates new embeddings, and updates Supabase so the next answer reflects the updated policy. No manual refresh, no “did you see the new doc?” reminders.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your team gets 15 policy questions a week in Telegram, and each one takes about 10 minutes to clarify, find the right doc, and reply. That’s roughly 2.5 hours, and honestly it’s usually more once the thread spirals. With this workflow, each question is sent once (or spoken as a voice note), and the bot replies in about a minute after it searches Supabase and generates an answer. You still review the occasional edge case, but you stop paying the “constant interruption tax.”

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram for your team’s chat-based Q&A.
  • Google Drive to store policies, FAQs, and docs.
  • Supabase to store embeddings and run vector search.
  • OpenAI API key (get it from your OpenAI dashboard) for transcription, embeddings, and answers.

Skill level: Intermediate. You’ll connect accounts, paste API keys, and do light testing with a few real questions.

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

How It Works

A Telegram message kicks it off. The workflow triggers when your bot receives a new message. A Switch node routes the request based on what the user sent, so voice notes don’t get treated like plain text.

Voice gets turned into text. If the message includes audio, n8n fetches the file from Telegram and sends it to OpenAI for transcription. Short voice notes come back quickly. Longer ones sometimes need a little extra wait time.

The assistant searches your docs, not the open internet. The RAG agent takes the question, generates embeddings, and queries the Supabase vector store to find the most relevant chunks from your Drive files. Then it uses an OpenAI chat model to write a helpful answer based on that context, which reduces “hallucinated” replies.

Answers land back in Telegram. The final message is posted into the same Telegram thread so the user can move on. No doc links required, though you can add them if your team prefers to read the source.

You can easily modify the data source and destination to fit your setup. For example, swap Telegram for Slack, or narrow search to HR-only docs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Google Drive and Telegram Triggers

Set up the incoming event sources that start the ingestion and query flows: Google Drive for file changes and Telegram for user queries.

  1. Open New File Trigger and set Event to fileCreated and Trigger On to specificFolder.
  2. In New File Trigger, choose the folder under Folder to Watch and replace [YOUR_ID] with your Drive folder ID.
  3. Credential Required: Connect your googleDriveOAuth2Api credentials in New File Trigger.
  4. Open File Update Trigger and set Event to fileUpdated and Trigger On to specificFolder.
  5. Credential Required: Connect your googleDriveOAuth2Api credentials in File Update Trigger.
  6. Open Telegram Message Trigger and keep Updates set to message.
  7. Credential Required: Connect your telegramApi credentials in Telegram Message Trigger.
⚠️ Common Pitfall: If the Drive triggers do not fire, confirm the correct folder ID is selected under Folder to Watch and that the connected account has access.

Step 2: Connect Google Drive Download and Initial Vector Ingestion

This path ingests newly created files, extracts text, and inserts vectors into Supabase.

  1. In Assign Record ID, set the id assignment to {{ $json.id }}.
  2. In Drive File Download, set Operation to download and File ID to {{ $json.id }}.
  3. In Drive File Download, enable Google Docs conversion by setting Docs to Format to text/plain.
  4. Credential Required: Connect your googleDriveOAuth2Api credentials in Drive File Download.
  5. In Extract Text Content, set Operation to text.
  6. In Recursive Text Divider, set Chunk Size to 500 and Chunk Overlap to 100.
  7. In Standard Data Loader, set the metadata value file_id to {{ $('Assign Record ID').item.json.id }}.
  8. In Supabase Vector Index, set Mode to insert and Table Name to documents.
  9. Credential Required: Connect your supabaseApi credentials in Supabase Vector Index.
  10. Credential Required: Connect your openAiApi credentials in OpenAI Embedding Builder (used for embeddings into Supabase Vector Index).

Step 3: Configure File Update Re-Indexing

This path deletes existing vectors for updated files and re-ingests fresh content.

  1. In Remove Matching Rows, set Table to documents, Operation to delete, and Filter String to =metadata->>file_id=like.*{{ $json.id }}*.
  2. Credential Required: Connect your supabaseApi credentials in Remove Matching Rows.
  3. In Capture File Identifier, set file_id to {{ $('File Update Trigger').item.json.id }}.
  4. In Drive File Download A, set File ID to {{ $('Capture File Identifier').item.json.file_id }} and Operation to download.
  5. Credential Required: Connect your googleDriveOAuth2Api credentials in Drive File Download A.
  6. In Extract Text Content A, set Operation to text, then use Recursive Text Divider A with Chunk Size 300 and Chunk Overlap 50.
  7. In Standard Data Loader A, set metadata file_id to {{ $('Normalize Records').item.json.file_id }}.
  8. In Supabase Vector Index A, set Mode to insert and Table Name to documents.
  9. Credential Required: Connect your supabaseApi credentials in Supabase Vector Index A and openAiApi credentials in OpenAI Embedding Builder A.

Step 4: Route Telegram Input and Handle Voice Transcription

This section determines whether the Telegram message is text or voice, then prepares the query for the assistant.

  1. In Route Voice or Text, keep the two rules that check {{ $json.message.voice.file_id }} and {{ $json.message.text }} with exists conditions.
  2. For voice messages, Route Voice or Text sends output to Telegram File Fetch (voice branch).
  3. In Telegram File Fetch, set Resource to file and File ID to {{ $json.message.voice.file_id }}.
  4. Credential Required: Connect your telegramApi credentials in Telegram File Fetch.
  5. In Transcribe Audio, set Resource to audio and Operation to transcribe.
  6. Credential Required: Connect your openAiApi credentials in Transcribe Audio.
  7. For text messages, Route Voice or Text sends output to Map Text Input, which maps text to {{ $json.message.text }}.

Step 5: Set Up the RAG Assistant and Vector Tooling

Configure the assistant to use the Supabase vector store and maintain conversation memory.

  1. In RAG Assistant, set Text to {{ $json.text }} and keep Prompt Type as define with the provided system message.
  2. Connect OpenAI Chat Model B as the language model for RAG Assistant; set Model to gpt-4o.
  3. Credential Required: Connect your openAiApi credentials in OpenAI Chat Model B.
  4. In Window Buffer Memory, set Session Key to {{ $('Telegram Message Trigger').item.json.message.chat.id }} and Session ID Type to customKey.
  5. In Vector Store Tool, keep Name as MarketingLadder and Description as This vector store holds information about Marketing Ladder agency.
  6. Ensure Supabase Vector Index B is connected as the vector store for Vector Store Tool; it uses Table Name documents.
  7. Credential Required: Connect your supabaseApi credentials in Supabase Vector Index B and openAiApi credentials in OpenAI Embedding Builder B.
  8. OpenAI Chat Model A is connected as the language model for Vector Store Tool — ensure credentials are added to OpenAI Chat Model A, not the tool node.

Step 6: Configure the Telegram Reply Output

Send the assistant’s response back to the user in Telegram.

  1. In Send Telegram Reply, set Text to {{ $json.output }}.
  2. Set Chat ID to {{ $('Telegram Message Trigger').item.json.message.chat.id }}.
  3. Credential Required: Connect your telegramApi credentials in Send Telegram Reply.

Step 7: Test and Activate Your Workflow

Validate both ingestion and query flows before running in production.

  1. Click Execute Workflow and upload a new file to the watched Drive folder to verify New File Trigger → Drive File Download → Extract Text Content → Supabase Vector Index.
  2. Update an existing file to verify File Update Trigger → Remove Matching Rows → Drive File Download A → Supabase Vector Index A.
  3. Send both a text and a voice message to your Telegram bot and confirm Route Voice or Text routes correctly and Send Telegram Reply returns a response.
  4. Successful execution should show vector inserts in Supabase and a Telegram reply generated from RAG Assistant.
  5. When satisfied, toggle the workflow to Active for continuous operation.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Drive credentials can expire or lack access to the shared folder. If new files aren’t indexing, check the n8n credential permissions and the folder share settings first.
  • If you’re using Wait nodes or external processing (like transcription), processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Supabase tables and policies can block inserts if Row Level Security is on without the right service key. If vector upserts fail, check Supabase logs and confirm you’re using the correct API key for server-side writes.

Related Workflows

If you like the idea of answers in chat but also want a proper backend you can query and audit, pair this with Google Drive to Supabase, a living knowledge base so your document updates are organized beyond just messaging.

For teams living in Slack instead of Telegram, Google Drive + Slack: instant policy answers for teams is the closest sibling workflow and makes adoption easier for Slack-first companies.

When support is drowning in repeat tickets and you want AI to draft replies without losing your tone, Zendesk + OpenAI: faster first replies, consistent tone complements this nicely. One handles internal Q&A, the other handles customer-facing volume.

Need a way to capture questions from your site and make sure nothing falls through the cracks? OpenAI + Gmail, website chats routed and logged is useful when your “chat” starts on the website but your team still wants an email-based workflow and a record.

Finally, if your knowledge base includes external sites (competitors, docs portals, public help centers), Apify to Supabase, turn sites into searchable answers helps you scrape, structure, and search that content alongside internal documents.


Quick reference:

Frequently Asked Questions

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

About 60–90 minutes if your Drive folder and Supabase project are ready.

Do I need coding skills to automate Drive Telegram answers?

No. You’ll connect accounts, paste a few API keys, and test with real questions.

Is n8n free to use for this Drive Telegram answers 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 API usage, which is usually a few dollars a month for small teams (more if you transcribe lots of voice).

Where can I host n8n to run this Drive Telegram answers 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 Drive Telegram answers workflow for Slack instead of Telegram?

Yes, but you’ll swap the Telegram Message Trigger and Send Telegram Reply nodes for Slack equivalents, then keep the RAG Assistant and Supabase vector search pieces the same. Many teams also tweak the assistant prompt to match their internal style guide and add a short “source” line that cites the file name. If you want department-specific answers, add metadata during indexing (like “HR” or “Engineering”) and filter your vector search to only pull the right documents.

Why is my Telegram connection failing in this Drive Telegram answers workflow?

Usually it’s an invalid bot token or the bot isn’t allowed to read the chat you’re testing in. Regenerate the token in BotFather, update the Telegram credentials in n8n, and confirm the bot has been added to the group (with permission to read messages). If voice messages fail but text works, check that the Telegram File Fetch step is receiving a file_id and that OpenAI transcription has a valid API key.

How many questions can this Drive Telegram answers automation handle?

Plenty for a small team. On n8n Cloud Starter you’re limited by monthly executions, while self-hosting has no fixed cap (it depends on your server). In practice, the bottlenecks are usually OpenAI rate limits and how many documents you’ve indexed, not n8n itself.

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

For a RAG assistant like this, yes more often than not. You need branching logic (voice vs. text), file handling, chunking, embeddings, and a vector database update loop when Drive files change. n8n is built for that kind of multi-step flow, and self-hosting is a big deal when usage grows. Zapier or Make can work for simpler “send message when file changes” tasks, but they get awkward and expensive once you add memory, retrieval, and document sync. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation.

Once this is running, “Where do I find that?” turns into a one-minute answer in chat. Set it up, keep your docs clean, and let the workflow handle the repeat pings.

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.