Nutrition tracker & meal logger with Telegram, Gemini AI and Google Sheets

32823 views

2/3/2026

Forms Approval Automation Salesforce CRM

🤖🥗 Telegram Nutrition AI Assistant (Alternative to Cal AI App)

> AI-powered nutrition assistant for Telegram — log meals, set goals, and get personalized daily reports with Google Sheets integration.

📋 Description

This n8n template creates a Telegram-based Nutrition AI Assistant 🥑🔥 designed as an open-source alternative to the Cal AI mobile app. It allows users to interact with an AI agent via text, voice, or images to track meals, calculate macros, and monitor nutrition goals directly from Telegram.

The system integrates Google Sheets as the database, handling both user profiles and meal logs, while leveraging Gemini AI for natural conversation, food recognition, and daily progress reports.

✨ Key Features

💬 Multi-input support: Text, voice messages (transcribed), and food images (AI analysis).
📊 Macro calculation: Automatic estimation of calories, proteins, carbs, and fats.
📝 User-friendly registration: Simple onboarding without storing personal health data (no weight/height required).
🎯 Goal tracking: Users can set and update calorie and protein targets.
📈 Daily reports: Personalized progress messages with visual progress bars.
🗂 Google Sheets integration:
- Profile table for user targets.
- Meals table for food logs.
🔄 Advanced n8n nodes: Includes use of Merge, Subworkflow, and Code nodes for data processing and report generation.

💡 Acknowledgment

Inspired by the Cal AI concept 💡 — this template demonstrates how to reproduce its main functionality with n8n, Telegram, and AI agents as a flexible, open-source automation workflow.

💼 Use Case

Use this template if you want to:

🥗 Log meals using text, images, or voice messages.
📊 Track nutrition goals (calories, proteins) with daily progress updates.
🤖 Provide a chat-based nutrition assistant without building a full app.
🗂 Store structured nutrition data in Google Sheets for easy access and analysis.

💬 Example User Interactions

📸 User sends a photo of a meal → AI analyzes the food and logs calories/macros.
🎤 User sends a voice message → AI transcribes and logs the meal.
⌨️ User types “report” → AI returns a daily nutrition summary with progress bars.
🥅 User says “update my protein goal” → AI updates profile in Google Sheets.

🔑 Required Credentials

Telegram Bot API (Bot Token)
Google Sheets API credentials
AI Provider API (Google Gemini or compatible LLM)

⚙️ Setup Instructions

🗂 Create two Google Sheets tables:
- Profile: User_ID, Name, Calories_target, Protein_target
- Meals: User_ID, Date, Meal_description, Calories, Proteins, Carbs, Fats
🔌 Configure the Telegram Trigger with your bot token.
🤖 Connect your AI provider credentials (Gemini recommended).
📑 Connect Google Sheets with your credentials.
▶️ Deploy the workflow in n8n.
🎯 Start interacting with your nutrition assistant via Telegram.

📌 Extra Notes

🟩 Green section: Handles Telegram trigger and user check.
🟥 Red section: Registers new users and sets goals.
🟦 Blue section: Processes text, voice, and images.
🟨 Yellow section: Generates nutrition reports.
🟪 Purple section: Main AI agent controlling tools and logic.

💡 Need Assistance?

If you’d like help customizing or extending this workflow, feel free to reach out:

📧 Email: johnsilva11031@gmail.com
🔗 LinkedIn: John Alejandro Silva Rodríguez

n8n Nutrition Tracker & Meal Logger with Telegram, Gemini AI, and Google Sheets

This n8n workflow provides a powerful and convenient way to track your meals and nutrition using a Telegram bot, Gemini AI, and Google Sheets. Simply send your meal descriptions to the bot, and the AI will analyze them to extract nutritional information, which is then logged into a Google Sheet.

What it does

This workflow automates the following steps:

Listens for Telegram Messages: Triggers when a new message is received by your configured Telegram bot.
Initial Telegram Response: Immediately sends a "Thinking..." message back to the user to acknowledge receipt and provide feedback.
AI Agent Processing: Utilizes a Google Gemini AI Agent to interpret the user's meal description.
- It employs a "Simple Memory" to maintain context within the conversation.
- It uses an "n8n Workflow Tool" to interact with other parts of the n8n system, likely for data logging.
Extracts AI Response: Processes the output from the AI agent, which should contain the extracted nutritional data.
Conditional Logging: Checks if the AI successfully extracted nutritional information.
- If successful:
  - Prepares the data by setting fields like timestamp, meal, calories, protein, carbs, and fat.
  - Appends this structured nutritional data as a new row to a specified Google Sheet.
  - Sends a confirmation message back to the Telegram user, including the logged details.
- If unsuccessful:
  - Sends an error message to the Telegram user, indicating that the meal could not be parsed and suggesting a rephrase.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance (self-hosted or cloud).
Telegram Bot: A Telegram bot token and chat ID. You can create a bot using BotFather on Telegram.
Google Sheets Account: A Google account with access to Google Sheets. You'll need to create a new spreadsheet for logging your meals.
Google Gemini AI Credentials: An API key or credentials for Google Gemini (or a compatible LLM configured within the Google Gemini Chat Model node).
n8n Credentials: Appropriate n8n credentials for Telegram, Google Sheets, and Google Gemini.

Setup/Usage

Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three-dot menu in the top right and select "Import from JSON".
- Paste the workflow JSON or upload the file.
Configure Credentials:
- Telegram Trigger (Node 50) & Telegram (Node 49):
  - Click on the "Telegram Trigger" node and configure your Telegram Bot API credentials.
  - Ensure the "Telegram" node also uses the correct credentials.
  - Note down your Chat ID from the Telegram Trigger's output after a test message, as you might need it for the "Telegram" nodes to send messages back.
- Google Gemini Chat Model (Node 1262):
  - Configure your Google Gemini API credentials.
- Google Sheets (Node 18):
  - Configure your Google Sheets credentials.
  - Specify the Spreadsheet ID and Sheet Name where you want to log your meals. Ensure the sheet has columns for timestamp, meal, calories, protein, carbs, and fat.
Activate the Workflow:
- Once all credentials are set up and the workflow is configured, activate it by toggling the "Active" switch in the top right corner of the workflow editor.
Start Logging:
- Send a message to your Telegram bot describing your meal (e.g., "I ate a chicken salad with avocado and a side of rice. Estimated 450 calories, 30g protein, 40g carbs, 20g fat").
- The bot will respond with "Thinking...", process your input, and then confirm the logged meal details in Telegram and add a new row to your Google Sheet.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

By Ranjan Dailata

161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

By Daniel Nkencho

601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

By Le Nguyen

942