🔓 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 Sheets, effortless meal logs

Telegram to Google Sheets, effortless meal logs - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram to Google Sheets, effortless meal logs - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Meal tracking usually falls apart the same way. You start strong, then the logging gets annoying, the data gets messy, and “I’ll do it later” turns into three missed days.

Telegram meal logs hit home for Coaches who need clients to actually follow through. Founders and busy marketers feel it too, because no one wants another app or another spreadsheet tab to keep up with.

This n8n workflow turns Telegram into a lightweight nutrition assistant. You’ll see how it captures meals from text, voice, or photos, writes clean rows to Google Sheets, and sends a clear daily progress summary back to you.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram to Google Sheets, effortless meal logs

The Problem: Meal tracking breaks when logging is a chore

Manual meal tracking sounds simple until you live with it. You eat something, then you have to remember what it was, estimate portions, open an app, search foods, adjust macros, and hope you didn’t pick the wrong “chicken bowl” from the list of fifty. Then you try to summarize the day, and it turns into more tapping. The real cost isn’t just time; it’s the mental friction that makes you stop logging at all. And once entries are inconsistent, the “daily report” becomes a vague guess instead of something you can act on.

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

  • Logging each meal takes about 5–10 minutes, so a normal day can quietly eat 30 minutes.
  • Photo meals are the worst to capture cleanly, because you still end up typing the details later.
  • Macros end up inconsistent when you switch between apps, notes, and “I’ll remember it.”
  • You can’t get a reliable daily summary if half your meals never make it into the system.

The Solution: Log meals in Telegram, store clean data in Sheets

This workflow turns a Telegram chat into your input layer, and Google Sheets into your database. A message comes in (text, a voice note, or a food photo), the workflow routes it to the right handler, and an AI model interprets what you ate. That interpretation gets normalized into consistent fields (meal description plus calories, protein, carbs, fats), then appended to a “Meals” table in Google Sheets. If you’re new, it also runs a simple registration flow to create a profile row with your calorie and protein targets, so the assistant has context. When you ask for a report (or when the report trigger runs), it pulls today’s meals and your targets, aggregates totals, builds a progress-style message, and sends it back in Telegram.

The workflow starts with a Telegram intake trigger, then checks whether you’re registered. From there it routes messages by type (text, voice, image), extracts nutrition details, and writes a clean row to Google Sheets. Finally, a reporting sub-workflow generates a daily summary that’s easy to understand in one glance.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you log 4 meals a day. Manually, if each entry takes about 7 minutes (searching foods, estimating macros, fixing mistakes), that’s roughly 30 minutes daily. With this workflow, you send a quick Telegram message or photo in about a minute per meal, then let the AI do the interpretation and the sheet logging in the background. Even if you wait a few minutes for transcription or image analysis, your hands-on time drops to about 5 minutes total. That’s about 25 minutes back every day, and the data is cleaner.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram to collect meal messages and media.
  • Google Sheets to store profiles and meal logs.
  • AI provider API key (get it from Google AI Studio for Gemini, or your LLM provider).

Skill level: Intermediate. You’ll connect credentials, create two Sheets tables, and adjust a couple of message prompts.

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

How It Works

A Telegram message triggers the workflow. Your bot receives text, a voice note, or an image through the Telegram Trigger, then sends a quick “typing” indicator so the chat feels responsive.

The workflow checks if the user is registered. It looks you up in the Google Sheets “Profile” table. If you’re new, a registration assistant collects your calorie and protein targets and appends a profile row.

Inputs are routed and interpreted. A Switch node routes by message type. Voice notes are fetched and transcribed, images are fetched and analyzed, and plain text is mapped directly into the AI agent context.

Meal entries and daily reports are produced. For logging, the workflow appends a row to the “Meals” table (description plus macros). For reporting, a report trigger pulls meals and targets, totals the day, builds a readable progress message, then sends it back to Telegram.

You can easily modify the targets you track (for example, add carbs or fats goals) to match 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 Telegram message arrives and immediately branches to registration lookup and typing indicator in parallel.

  1. Add the Telegram Intake Trigger node.
  2. Credential Required: Connect your telegramApi credentials.
  3. Set Updates to message.
  4. Confirm the execution flow: Telegram Intake Trigger outputs to both Lookup Registration and Send Typing Indicator in parallel.

Tip: If the trigger isn’t receiving updates, re-save the node to refresh the Telegram webhook registration.

Step 2: Connect Google Sheets

Google Sheets powers user profiles and meal logs, and it also supports AI tools for registration and meal storage.

  1. Open Lookup Registration and set Document ID to [YOUR_ID] and Sheet Name to Profile.
  2. Ensure the Filters in Lookup Registration use {{$('Telegram Intake Trigger').item.json.message.chat.id}} mapped to User_ID.
  3. Configure Retrieve Meal Records with Document ID [YOUR_ID] and Sheet Name Meals, and add filters for {{$json.Date}} and {{$json.User_ID}}.
  4. Configure Retrieve Profile Records with Document ID [YOUR_ID] and Sheet Name Profile.
  5. Credential Required: Connect your googleSheetsOAuth2Api credentials to Lookup Registration, Retrieve Meal Records, and Retrieve Profile Records.
  6. Connect the same googleSheetsOAuth2Api credentials to all Google Sheets tool nodes: Append Profile Row, Update Profile Targets, Fetch Profile Targets, and Append Meal Entry.

⚠️ Common Pitfall: Leaving [YOUR_ID] unchanged will cause all Google Sheets nodes to fail. Replace it with your actual spreadsheet ID.

Step 3: Set Up Registration Routing

Incoming chats are checked against the Profile sheet to route new users to registration or existing users to intake processing.

  1. In Check Registration, keep the condition that checks {{$json.User_ID}} exists.
  2. Connect Lookup Registration → Check Registration → Route Incoming Message (registered users) and Map Registration Text (new users).
  3. In Map Registration Text, set message to {{$('Telegram Intake Trigger').item.json.message.text}} and chat_id to {{$('Telegram Intake Trigger').item.json.message.chat.id}}.
  4. Keep the flow Map Registration Text → Registration Assistant → Format Markdown Reg → Dispatch Registration Reply.

Tip: Registration uses the AI tools and memory attached to Registration Assistant, so you don’t need to modify the sub-nodes directly.

Step 4: Configure Intake Routing and Media Handling

The workflow routes text, voice, image, or unsupported files and prepares consistent payloads for the AI coach.

  1. In Route Incoming Message, keep the three rules that check for {{$('Telegram Intake Trigger').item.json.message.text}}, {{$('Telegram Intake Trigger').item.json.message.voice}}, and {{$('Telegram Intake Trigger').item.json.message.photo[0].file_id}}.
  2. For text: ensure Map Text Payload sets message to {{$('Telegram Intake Trigger').item.json.message.text}} and chat_id to {{$('Telegram Intake Trigger').item.json.message.chat.id}}.
  3. For voice: configure Fetch Voice File with File ID {{$('Telegram Intake Trigger').item.json.message.voice.file_id}} then connect to Normalize MIME Audio → Interpret Audio Message → Map Audio Payload.
  4. For image: configure Fetch Image File with File ID {{$('Telegram Intake Trigger').item.json.message.photo[3]?.file_id || $('Telegram Intake Trigger').item.json.message.photo[2]?.file_id || $('Telegram Intake Trigger').item.json.message.photo[1]?.file_id}} then connect to Normalize MIME Image → Interpret Image Nutrition → Map Image Payload.
  5. For unsupported files: keep Map Unsupported File Notice passing the fallback message to Nutrition Coach Agent.
  6. Credential Required: Connect your telegramApi credentials to Fetch Voice File, Fetch Image File, and Send Typing Indicator.

Tip: The two Normalize MIME code nodes are critical for Gemini to accept Telegram file binaries—do not remove them.

Step 5: Set Up AI Models and Memory

The workflow uses Gemini for media interpretation and two AI agents for registration and coaching.

  1. Credential Required: Connect your googlePalmApi credentials to Interpret Image Nutrition and Interpret Audio Message.
  2. Credential Required: Connect your googlePalmApi credentials to Gemini Chat Model and Gemini Chat Model Reg.
  3. Ensure Gemini Chat Model is connected as the language model for Nutrition Coach Agent.
  4. Ensure Gemini Chat Model Reg is connected as the language model for Registration Assistant.
  5. Keep memory nodes attached to their parent agents: Conversation Memory connects to Nutrition Coach Agent and Registration Memory connects to Registration Assistant.
  6. For memory nodes, keep Session Key set to {{$json.chat_id}} and Session ID Type set to customKey.

⚠️ Common Pitfall: AI sub-nodes like Conversation Memory and Registration Memory do not take credentials directly—add them to Gemini Chat Model and Gemini Chat Model Reg instead.

Step 6: Configure AI Tools for Sheets and Reports

AI tools let the agents append meals, update profiles, and generate reports without manual branching.

  1. In Append Meal Entry, confirm Date uses {{$today.format("yyyy-LL-dd")}} and fields map from $fromAI() inputs.
  2. In Append Profile Row and Update Profile Targets, keep the mapping that uses {{$json.chat_id}} as User_ID and $fromAI() values for targets.
  3. In Fetch Profile Targets, keep the lookup filter {{$json.chat_id}} for User_ID.
  4. In Run Daily Report, keep Workflow ID as {{$workflow.id}} and inputs {{$fromAI('Date', ``, 'string')}} plus {{$json.chat_id}}.
  5. Remember these are AI tools: credentials are applied to the tool nodes themselves, while the calling agent is Nutrition Coach Agent or Registration Assistant.

Step 7: Configure Daily Report Branch

The daily report is a parallel data fetch that merges meals and profile records to produce a formatted summary.

  1. Confirm the parallel branch: Report Trigger outputs to both Retrieve Meal Records and Retrieve Profile Records in parallel.
  2. Keep Retrieve Meal Records → Extract Meal Totals → Aggregate Nutrition Totals.
  3. Keep Aggregate Nutrition Totals and Retrieve Profile Records merging in Combine Report Data.
  4. Connect Combine Report Data → Build Report Message → Prepare Report Reply.

Step 8: Configure Telegram Output Formatting

Both the registration flow and the coaching flow format messages safely for Telegram MarkdownV2 before sending.

  1. Keep Nutrition Coach Agent → Format MarkdownV2 → Dispatch Telegram Reply.
  2. Keep Registration Assistant → Format Markdown Reg → Dispatch Registration Reply.
  3. In Dispatch Telegram Reply and Dispatch Registration Reply, set Text to {{$json.message}} and Chat ID to {{$('Telegram Intake Trigger').item.json.message.chat.id}}.
  4. Credential Required: Connect your telegramApi credentials to Dispatch Telegram Reply and Dispatch Registration Reply.

Tip: The code nodes Format MarkdownV2 and Format Markdown Reg auto-chunk long messages—leave them in “Run Once for All Items” mode.

Step 9: Test and Activate Your Workflow

Validate both the registration and coaching branches with sample Telegram messages and a report request.

  1. Click Execute Workflow and send a Telegram text message to trigger Telegram Intake Trigger.
  2. Send a photo and a voice note to verify Fetch Image File → Interpret Image Nutrition and Fetch Voice File → Interpret Audio Message paths.
  3. Confirm successful output: Dispatch Telegram Reply should send MarkdownV2-safe responses.
  4. Trigger a report via the agent and verify Build Report Message creates a summary and Prepare Report Reply passes it through.
  5. 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 Sheets credentials can expire or need specific permissions. If things break, check the n8n credential connection test and make sure the Google account can edit the sheet.
  • 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 like the idea of meal logging but want a more “assistant-style” chat that leans heavily on Gemini, Telegram + Google Gemini, meal logs without spreadsheets is a natural companion for testing different conversation flows.

When your biggest pain is photos (and getting consistent descriptions from them), Telegram to Google Sheets, meal photos logged neatly focuses more directly on that capture-and-cleanup loop.

For teams or clients who don’t use Telegram much, LINE + Google Sheets: meal photos logged with insights gives you the same “message in, structured rows out” pattern in a different chat app.

Need stricter formatting so the sheet never turns into a junk drawer? Telegram to Google Sheets, meal logs that stay clean is helpful when you care about analysis later (weekly averages, coaching audits, dashboards).

Finally, if you’re already automating personal admin in Telegram, Telegram to Google Sheets, receipts logged instantly pairs well because it uses the same habit: send a photo, get clean data stored automatically.


Quick reference:

Frequently Asked Questions

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

About an hour if you already have your Telegram bot and Google credentials ready.

Do I need coding skills to automate Telegram meal logs?

No. You will mainly connect accounts and copy the provided Google Sheets column headers.

Is n8n free to use for this Telegram meal logs 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 API usage, which is usually a few cents per day for personal logging.

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 meal logs workflow for weekly check-ins instead of daily reports?

Yes, but you’ll change the reporting trigger. Swap the current report trigger behavior to run on a schedule, then adjust the “Retrieve Meal Records” query window and the “Build Report Message” formatting to summarize a week. Many teams also tweak the agent prompt so it highlights trends (like “protein low on weekends”) instead of day totals.

Why is my Telegram connection failing in this workflow?

Usually it’s a bot token issue or the bot isn’t actually receiving updates. Confirm the token in your Telegram Trigger credentials, then send a fresh message to the bot and check n8n’s execution log to see if the trigger fired. If it fired but file downloads fail, the “Fetch Voice File” or “Fetch Image File” step may be missing permissions or referencing an expired file_id.

How many meals can this Telegram meal logs automation handle?

For a single person, it’s effectively unlimited.

Is this Telegram meal logs automation better than using Zapier or Make?

Often, yes, if you want the AI assistant behavior. n8n handles branching logic (text vs. voice vs. image), conversation memory, and multi-step reporting without turning into a pricey chain of premium tasks. Zapier or Make can still work for basic “Telegram message to Google Sheets row,” but the moment you add transcription, image analysis, and a daily report, the workflow gets awkward. n8n is also easier to self-host, which matters if you’re running this for many users. If you’re deciding between tools, Talk to an automation expert and we’ll map it to your volume and budget.

Once this is running, logging becomes a quick message instead of a daily negotiation with yourself. The workflow handles the repetitive stuff, and you get clean data plus a report you can actually use.

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.