Telegram + Google Sheets: orders logged, no chaos
Orders coming in through Telegram sounds convenient. Until your “order system” becomes a pile of voice notes, half-complete addresses, and screenshots you swear you’ll log later.
Shop owners feel it first. Then your marketing lead gets pulled into support, and your customer service teammate ends up copy-pasting all day. This Telegram order logging automation turns messy chats into clean rows in Google Sheets, so you stop losing orders (and your patience).
Below you’ll see exactly what the workflow does, what you get out of it, and what it takes to run it without babysitting.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram + Google Sheets: orders logged, no chaos
flowchart LR
subgraph sg0["Telegram Flow"]
direction LR
n0["<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/>Telegram Trigger"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set 'Text'", pos: "b", h: 48 }
n2["<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/>Download Voice File"]
n3@{ icon: "mdi:robot", form: "rounded", label: "Transcribe Audio", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Switch", pos: "b", h: 48 }
n5["<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/>Response"]
n6@{ icon: "mdi:robot", form: "rounded", label: "AI Agent1", pos: "b", h: 48 }
n7@{ icon: "mdi:wrench", form: "rounded", label: "Answer questions with a vect..", pos: "b", h: 48 }
n8@{ icon: "mdi:cube-outline", form: "rounded", label: "Pinecone Vector Store", pos: "b", h: 48 }
n9@{ icon: "mdi:vector-polygon", form: "rounded", label: "Embeddings OpenAI1", pos: "b", h: 48 }
n10@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model4", pos: "b", h: 48 }
n12@{ icon: "mdi:database", form: "rounded", label: "Append row in sheet in Googl..", pos: "b", h: 48 }
n13@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", pos: "b", h: 48 }
n4 --> n2
n4 --> n1
n6 --> n5
n1 --> n6
n13 -.-> n6
n0 --> n4
n3 --> n6
n10 -.-> n6
n9 -.-> n8
n11 -.-> n7
n2 --> n3
n8 -.-> n7
n12 -.-> n6
n7 -.-> n6
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 n0 trigger
class n3,n6 ai
class n10,n11 aiModel
class n7 ai
class n13 ai
class n8 ai
class n9 ai
class n4 decision
class n12 database
classDef customIcon fill:none,stroke:none
class n0,n2,n5 customIcon
The Problem: Telegram Orders Get Messy Fast
Taking orders in Telegram is great for customers because it feels like a quick chat. For you, it’s a slow-motion breakdown. One person sends a voice note with the address. Another asks three product questions before they even mention size. Someone else says “same as last time” and disappears. You can’t search it cleanly, you can’t hand it off neatly, and when you finally log it into a sheet, you’re relying on memory. That’s when mistakes sneak in: wrong category, missing phone number, duplicate orders, and awkward follow-ups.
It adds up fast. Here’s where it breaks down in real life.
- You spend about 10 minutes per order just extracting the basics (name, phone, address, product).
- Voice notes slow everything down because you have to replay them, and you still miss details.
- Product answers drift over time, so two customers get two different “official” prices.
- When the chat scrolls, orders get lost, and you only notice after someone complains.
The Solution: An AI Telegram Shopping Assistant That Logs Orders
This workflow turns your Telegram bot into a practical sales assistant for your store. It listens for incoming Telegram messages in real time, and it handles both text and voice notes. If a customer sends a voice message, the workflow pulls the audio and transcribes it into text (so you’re not replaying clips all day). Then an AI Agent replies like a helpful human, using your product catalog as the source of truth, not guesswork. When the customer provides the required order details (name, phone, address, category), the workflow appends the order into Google Sheets automatically and confirms it back in Telegram.
The workflow starts with a Telegram Trigger. Messages get routed by type (text vs. voice), then normalized into one clean text stream for the AI Agent. Finally, complete orders land in Google Sheets, and the customer receives a clear confirmation message in the same chat.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your store gets 15 Telegram order conversations a day. Manually, you might spend about 10 minutes per conversation answering questions, replaying voice notes, and copying details into a sheet, which is roughly 2.5 hours daily. With this workflow, you mostly just monitor exceptions: customers get instant answers, voice notes become text automatically, and orders get logged the moment the required fields are captured. Realistically, you’re down to maybe 20 minutes total checking the sheet and stepping in for edge cases.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram for the customer chat and bot entrypoint
- Google Sheets to store orders in a shared log
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You will connect accounts, paste API keys, and tweak a few prompts and sheet column names.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A customer messages your Telegram bot. The Telegram Trigger picks up new messages instantly, including normal text and voice notes.
Voice notes get converted into usable text. If the incoming message is audio, the workflow downloads the recording and transcribes it with OpenAI’s Whisper, so the rest of the system treats it like a standard message.
The AI agent replies using your catalog, not vibes. The Customer Support Agent uses your Pinecone-backed knowledge base (RAG) to answer questions about prices, brands, and product details, and it keeps context with an 8-message memory window.
Orders get captured in Google Sheets. Once the conversation contains the required details (name, phone number, address, category), the workflow appends a new row to your sheet and sends a clear confirmation back in Telegram.
You can easily modify the required order fields to include things like delivery date or payment method based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Trigger
Set up the workflow to listen for incoming Telegram messages.
- Add and open Telegram Message Trigger.
- Set Updates to
message. - Credential Required: Connect your telegramApi credentials.
Step 2: Route Text vs Voice Messages
Use a switch to branch between text input and voice input, then map text fields for the AI agent.
- Open Route Message Type and verify it has two rules: one for voice and one for text.
- For the voice rule, ensure the condition checks
{{ $json.message.voice.file_id }}exists. - For the text rule, ensure the condition checks
{{ $json.message.text }}exists. - Open Map Text Fields and set text to
{{ $json.message.text }}. - Set chat_ID to
{{ $json.message.chat.id }}.
Step 3: Configure Voice Transcription
Fetch voice files and transcribe them to text before sending into the agent.
- Open Fetch Voice Recording and set Resource to
file. - Set File ID to
{{ $json.message.voice.file_id }}. - Credential Required: Connect your telegramApi credentials.
- Open Audio Transcription and set Resource to
audioand Operation totranscribe. - Credential Required: Connect your openAiApi credentials.
message.voice.file_id.Step 4: Set Up the AI Agent and Memory
Configure the AI agent with memory and language models for consistent multi-turn support.
- Open Customer Support Agent and confirm Text is set to
{{ $json.text }}. - Review the System Message in Customer Support Agent to ensure it matches your store policy and order capture requirements.
- Open Conversation Memory and set Session Key to
{{ $json.chat_ID }}, Session ID Type tocustomKey, and Context Window Length to8. - Open Primary Chat Model and set the model to
gpt-4.1-nano. - Credential Required: Connect your openAiApi credentials in Primary Chat Model.
Step 5: Connect Knowledge Base and Order Logging Tools
Wire the vector store Q&A tool and Google Sheets tool so the agent can answer questions and record orders.
- Open Pinecone Knowledge Store and set Pinecone Namespace to
mens-collection. - Credential Required: Connect your pineconeApi credentials.
- Open OpenAI Embeddings Builder and ensure it is connected to Pinecone Knowledge Store.
- Credential Required: Connect your openAiApi credentials in OpenAI Embeddings Builder.
- Open Vector Store Q&A Tool and confirm the Name is
mens_clothing_infowith the provided description. - Open Secondary Chat Model and set the model to
gpt-4.1-nano. - Credential Required: Connect your openAiApi credentials in Secondary Chat Model.
- Open Record Order in Sheets and set Operation to
append. - Set Document ID to
[YOUR_ID]and Sheet Name toSheet1. - Map columns using the AI expressions: Name
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Name', ``, 'string') }}, Address{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Address', ``, 'string') }}, Category{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Category', ``, 'string') }}, and Phone number{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Phone_number', ``, 'string') }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials.
Step 6: Configure the Telegram Reply Output
Send the agent’s output back to the same Telegram chat.
- Open Send Telegram Reply and set Text to
{{ $json.output }}. - Set Chat ID to
{{ $('Telegram Message Trigger').item.json.message.chat.id }}. - In Additional Fields, ensure Append Attribution is disabled.
- Credential Required: Connect your telegramApi credentials.
Step 7: Test and Activate Your Workflow
Validate the full path for both text and voice messages before going live.
- Click Execute Workflow and send a text message to your Telegram bot to verify Map Text Fields → Customer Support Agent → Send Telegram Reply.
- Send a voice message to verify Fetch Voice Recording → Audio Transcription → Customer Support Agent → Send Telegram Reply.
- Confirm that responses are generated and that order details are appended in Record Order in Sheets only after all four fields are collected.
- When satisfied, toggle the workflow to Active for production use.
Common Gotchas
- Telegram bot tokens get rotated more often than you’d think. If replies suddenly stop, check your Telegram credentials in n8n first and confirm the bot is still active in @BotFather.
- 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.
Frequently Asked Questions
About an hour if you already have your bot, sheet, and API keys ready.
No. You’ll mostly be connecting accounts and pasting API keys. The only “technical” part is being careful with your Google Sheet column names and the AI Agent instructions.
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 costs, which are usually low per conversation but depend on message volume and voice transcription usage.
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.
Yes, and you should. Update the AI Agent’s system instructions so it treats “Email” and “Delivery date” as required fields, then add matching columns in Google Sheets and map them in the “Record Order in Sheets” step. Many shops also add a “Payment method” field and a simple “Order status” column so fulfillment stays clean.
Usually it’s the bot token or permissions. Regenerate your Telegram bot token (or confirm it hasn’t changed), then update the Telegram credentials in n8n and re-test by sending a fresh message. Also check that you’re targeting the correct bot and that your workflow is active, because inactive workflows look like “Telegram is broken” when it’s really n8n not listening.
A lot. On n8n Cloud it depends on your plan’s execution limits, and on self-hosted it’s mostly your server size and how heavy your AI usage is. Practically, most small shops can handle daily order volume comfortably as long as you’re not transcribing huge voice notes all day.
Often, yes, if you need the AI Agent + memory + catalog lookup to work together. Zapier and Make can connect Telegram to Google Sheets, but conversational logic (voice transcription, context memory, and a knowledge base) gets clunky fast and can get pricey when volume rises. n8n also gives you a self-hosting option, which is honestly a big deal when you don’t want per-task billing. If your workflow is just “message comes in → add a row,” Zapier or Make is fine. If you’re not sure, Talk to an automation expert and pick the simplest tool that still fits.
You don’t need a better memory or more sticky notes. Set up the workflow once, and let Telegram conversations turn into a clean order log automatically, while you focus on fulfillment and growth.
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.
