Block 1 - Telegram Trigger
- Type / Role
- n8n-nodes-base.telegramTrigger - telegramTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Telegram Expense Tracker to Google Sheets with GPT 4.1 [
Message format is validated
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 fallbackIf valid:
If invalid:
Telegram Trigger nodeDate | Amount | Currency | Category | Description | SourceMessage
OpenAI Chat Model node using your OpenAI API keyrelevant, expense_record, and messageStructured Output Parser node to safely parse the JSON responseIs text message? Supported scenario? relevant = true in the LLM response| 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
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Track expenses from Telegram to Google Sheets with GPT-4.1 Mini |
|---|---|
| Complexity | advanced |
| Nodes | 23 |
| Categories | Personal Productivity, AI Summarization |
| Author | Trung Tran |
| Published | 04 Aug 2025 |
Use the JSON export at /data/workflows/6970/6970.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Telegram Expense Tracker to Google Sheets with GPT 4.1 [![Watch the video](https://s3.ap southeast 1.amazonaws.com/automatewith.me/track expenses from telegram to google sheets with gpt 41 mini+...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity, AI Summarization use case.