Track expenses from Telegram to Google Sheets with GPT-4.1 Mini
📒 Telegram Expense Tracker to Google Sheets with GPT-4.1
> A lightweight automation that lets users log daily expenses via a Telegram bot and instantly saves them into Google Sheets—perfect for anyone looking to manage spending on the go with AI-powered structure and ease.
👤 Who’s it for
This workflow is for anyone who wants to log their daily expenses by simply chatting with a Telegram bot. Ideal for:
- Individuals who want a quick way to track spending
- Freelancers who log receipts and purchases on the go
- Teams or small business owners who want lightweight expense capture
⚙️ How it works / What it does
-
User sends a text message on Telegram describing an expense
(e.g., “Bought coffee for 50k at Highlands”) -
Message format is validated
- If the message is text, it proceeds to GPT-4.1 Mini for processing.
- If it's not text (e.g. image or file), the bot sends a fallback message.
-
OpenAI GPT-4.1 Mini parses the message and returns:
relevant: true/falseexpense_record: structured fields (date, amount, currency, category, description, source)message: a friendly confirmation or fallback
-
If valid:
- The bot replies with a fun acknowledgment
- The data is saved to a connected Google Sheet
-
If invalid:
- A fallback message is sent to encourage proper input
🛠️ How to set up
1. Telegram Bot Setup
- Create a bot using BotFather on Telegram
- Copy the bot token and paste it into the
Telegram Triggernode
2. Google Sheet Setup
- Create a Google Sheet with these columns:
Date | Amount | Currency | Category | Description | SourceMessage - Share the sheet with your n8n service account email
3. OpenAI Configuration
- Connect the
OpenAI Chat Modelnode using your OpenAI API key - Use GPT-4.1 Mini as the model
- Apply a system prompt that extracts structured JSON with:
relevant,expense_record, andmessage
4. Add Parser
- Use the
Structured Output Parsernode to safely parse the JSON response
5. Conditional Logic Nodes
Is text message?- Checks if the message is in text format
Supported scenario?- Checks if
relevant = truein the LLM response
- Checks if
6. Final Actions
- If relevant:
- Send confirmation via Telegram
- Append row to Google Sheet
- If not relevant:
- Send fallback message via Telegram
✅ Requirements
- Telegram bot token
- OpenAI GPT-4.1 Mini API access
- n8n instance (self-hosted or cloud)
- Google Sheet with access granted to n8n
- Basic understanding of n8n node configuration
🧩 How to customize the workflow
| Feature | How to Customize |
|----------------------------------|-------------------------------------------------------------------|
| Add multi-currency support | Update system prompt to detect and extract different currencies |
| Add more categories | Modify the list of categories in the system prompt |
| Track multiple users | Add username or chat ID column to the Google Sheet |
| Trigger alerts | Add Slack, Email, or Telegram alerts for specific expense types |
| Weekly summaries | Use a cron node + Google Sheet query + Telegram message |
| Visual dashboards | Connect the sheet to Looker Studio or Google Data Studio |
Built with 💬 Telegram + 🧠 GPT-4.1 Mini + 📊 Google Sheets + ⚡ n8n
Track Expenses from Telegram to Google Sheets with AI Analysis
This n8n workflow automates the process of tracking expenses by capturing messages from Telegram, analyzing them with an AI agent (GPT-41-mini), and then recording the structured expense data into a Google Sheet. It also provides feedback to the user via Telegram.
What it does
This workflow streamlines expense tracking through the following steps:
- Listens for Telegram Messages: It acts as a Telegram bot, waiting for incoming messages from a user.
- Analyzes Message Content with AI: The received message is fed into an AI agent (configured with an OpenAI Chat Model and a Structured Output Parser). The AI is tasked with extracting key expense details like amount, currency, category, and a description.
- Parses AI Output: The AI's response, which is expected to be in a structured format (e.g., JSON), is then parsed to make the data usable.
- Conditional Processing: It checks if the AI successfully extracted a valid amount.
- If an amount is found: The extracted expense details (date, amount, currency, category, description) are appended as a new row to a specified Google Sheet. A confirmation message is sent back to the user on Telegram.
- If no amount is found: A message is sent back to the user on Telegram, asking them to provide a valid expense amount.
- Provides User Feedback: In both success and failure scenarios, the workflow communicates back to the user via Telegram, confirming the expense recording or requesting more information.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Telegram Bot Token: A Telegram bot set up with a BotFather token.
- OpenAI API Key: An API key for OpenAI (or a compatible service) to power the AI Chat Model.
- Google Account: Access to a Google account with a Google Sheet prepared for expense tracking.
- The Google Sheet should have columns corresponding to the data you expect to extract (e.g.,
Date,Amount,Currency,Category,Description).
- The Google Sheet should have columns corresponding to the data you expect to extract (e.g.,
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Telegram Trigger & Telegram Node: Set up your Telegram Bot API credential.
- OpenAI Chat Model Node: Set up your OpenAI API Key credential.
- Google Sheets Node: Set up your Google Sheets API credential (OAuth 2.0 is recommended).
- Configure Nodes:
- Telegram Trigger: Ensure it's configured to listen for messages from your desired chat(s).
- AI Agent:
- The "AI Agent" node will likely need instructions (a "prompt") on how to parse expense information from user messages. For example: "Extract the amount, currency, category, and a brief description from the following expense message. Output in JSON format with keys: 'amount', 'currency', 'category', 'description'."
- The "OpenAI Chat Model" node should be configured with your preferred model (e.g.,
gpt-4-miniif available, orgpt-3.5-turbo). - The "Structured Output Parser" node should be configured with the expected JSON schema that the AI agent will output.
- Code Node: This node will contain JavaScript logic to check if the AI successfully extracted an amount and to format the data for Google Sheets. You might need to adjust the logic to match the exact output of your AI agent.
- Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name where you want to record expenses.
- Ensure the "Operation" is set to "Append Row" and map the incoming data fields (e.g.,
{{ $json.amount }},{{ $json.category }}) to the correct columns in your Google Sheet.
- Telegram Nodes (for responses): Customize the success and failure messages sent back to the user.
- Activate the Workflow: Once configured, activate the workflow.
- Start Tracking: Send expense messages to your Telegram bot (e.g., "Spent $50 on groceries", "Lunch for 15 EUR at cafe"). The workflow will process them and update 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.
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
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.