🔓 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 + Google Sheets: approved expenses, logged

Telegram + Google Sheets: approved expenses, logged - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram + Google Sheets: approved expenses, logged - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Expense tracking falls apart in the tiny gaps. A receipt comes in while you’re on the move, you “mentally note it,” then your spreadsheet stays empty until it’s too late.

Freelancers feel it at tax time. A small business owner feels it when cash gets tight. And a financial assistant ends up chasing people for details. This Telegram expense logging automation puts every transaction into Google Sheets with an approval step, so nothing “disappears” between chat messages and month-end.

You’ll see how the workflow captures income and expenses in Telegram, validates the format, logs it to the right sheet tab, then routes expenses to a supervisor for Approve, Reject, or View Details.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram + Google Sheets: approved expenses, logged

The Problem: Expense tracking that depends on memory

Most “systems” for expenses are really just good intentions. Someone pays for something, tosses the receipt in a bag, and sends a quick message like “Taxi 18” or “Client lunch” with no context. Later, you open the spreadsheet and realize half the details are missing, some transactions were never recorded, and nobody remembers what was business vs. personal. It’s not only slow. It’s stressful, because every missing line item turns into back-and-forth, guessing, and last-minute cleanup.

The friction compounds. Here’s where it breaks down in real life.

  • You spend about 5 minutes per transaction translating casual chat messages into spreadsheet-ready entries.
  • Approvals happen in scattered places, so you can’t tell what’s final vs. still pending.
  • Formatting is inconsistent, which leads to wrong categories, duplicate rows, and messy closeouts.
  • Someone inevitably asks for “the status” and you end up manually checking the sheet and replying.

The Solution: Log transactions in Telegram, approve in one tap

This workflow turns Telegram into a lightweight finance intake form that people will actually use. A user starts the bot with /start, taps whether they’re logging income or an expense, then submits the transaction in a structured format (so details don’t get lost). n8n checks the message, parses the key fields, and writes the row into Google Sheets immediately. If it’s income, the user gets an instant confirmation and you’re done. If it’s an expense, the workflow marks it as pending, pings a supervisor in Telegram, and offers inline buttons to Approve ✅, Reject ❌, or View Details 👁. The user gets a clear outcome message once the supervisor decides.

The workflow starts with a Telegram Bot Trigger that captures messages and button clicks. It then routes based on message type (start, text input, or supervisor callback), writes or updates the correct row in Google Sheets, and sends the right notification back to the right person.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your team records 20 expenses a week. Manually, it’s usually “find the message, ask for missing details, enter the row, then update status later,” which is easily 5 minutes each, or about 2 hours weekly. With this workflow, logging is a quick Telegram message (call it 1 minute), and supervisor approval is a single tap when they see the prompt. You still wait for the decision, but you’re not doing the chasing or data entry.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram Bot for transaction intake and approvals
  • Google Sheets to store income and expense records
  • Google OAuth2 credentials (create in Google Cloud Console)

Skill level: Beginner. You’ll connect accounts, paste a bot token, and update a sheet ID and supervisor chat ID.

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

How It Works

Telegram message or button click triggers the workflow. The Telegram Bot Trigger captures both typed messages and inline button callbacks, which means the same automation handles intake and supervisor decisions.

The workflow figures out what kind of input it received. It separates “/start,” regular text submissions, and callback actions, then routes each one down the correct path so users aren’t stuck in the wrong menu.

Structured text gets validated and parsed into clean fields. A small set of logic nodes checks formatting, detects whether it’s income or expense, and extracts details that Google Sheets can store consistently.

Google Sheets is updated and the right people are notified. Income is appended to the income worksheet and confirmed back to the user. Expenses are logged to your expense tab, marked pending, and sent to a supervisor who can approve, reject, or request details without leaving Telegram.

You can easily modify the supervisor routing to support multiple approvers or different departments based on category. 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 or callback is received by Telegram Webhook Intake.

  1. Add and open Telegram Webhook Intake.
  2. Connect the Telegram bot that will receive messages and callbacks.
  3. Save the node so n8n registers the Telegram webhook.

Credential Required: Connect your Telegram credentials. Telegram credentials are required for Telegram Webhook Intake and all Telegram action nodes.

Step 2: Connect Google Sheets

The workflow writes and updates finance records in Google Sheets using multiple sheet nodes for income, expenses, and approvals.

  1. Open Log Income to Sheet and select the spreadsheet and worksheet where income should be stored.
  2. Open Log Expense to Sheet and select the expense worksheet for pending expenses.
  3. Open Modify Approval Status, Retrieve Approved Row, and Fetch Row for Detail View to point to the same approval tracking sheet.
  4. Ensure all Google Sheets nodes map to the same structure (columns for date, category, amount, notes, and approval status).

Credential Required: Connect your Google Sheets credentials. Google Sheets credentials are required for all sheet nodes.

Step 3: Set Up Message Classification & Routing

Incoming messages are categorized and routed through the core processing path for income/expense parsing.

  1. Review Identify Message Category to confirm it categorizes Telegram updates correctly before the workflow reaches Direct by Input Kind.
  2. Configure Direct by Input Kind to split between messages and callback queries, sending message flow to Process Start or Text and callback flow to Decode Callback Response.
  3. Set Process Start or Text to route text entries to Verify Input Structure and start messages to Display Income Expense Menu.
  4. In Verify Input Structure and Derive Data Category, validate input format and set the category before passing to Switch by Data Category.

⚠️ Common Pitfall: If Verify Input Structure rejects messages, users will never reach the income/expense logging path—validate your input parsing logic during testing.

Step 4: Configure Income/Expense Logging & Notifications

The income and expense paths parse the message, log data to sheets, and send confirmation messages.

  1. Ensure Switch by Data Category routes income to Interpret Income Details and expenses to Interpret Expense Details.
  2. In Interpret Income Details, map output fields expected by Log Income to Sheet.
  3. In Interpret Expense Details, map output fields expected by Log Expense to Sheet.
  4. Configure Confirm Income Logged to send a success message after Log Income to Sheet.
  5. Configure Alert Expense Pending to notify the user that approval is required after Log Expense to Sheet.
  6. Confirm Alert Expense Pending routes to Dispatch Approval Prompt to request supervisor approval.

Credential Required: Connect your Telegram credentials for Display Income Expense Menu, Confirm Income Logged, Alert Expense Pending, and Dispatch Approval Prompt.

Step 5: Configure Callback Approval & Detail Views

Callback buttons are decoded to update approval status, show detail views, and send format tips.

  1. In Decode Callback Response, parse callback data so Switch by Callback Type can route each action.
  2. Ensure Switch by Callback Type routes approvals to Modify Approval Status, then to Retrieve Approved Row, then to Send Approval Outcome.
  3. Ensure Switch by Callback Type routes detail requests to Fetch Row for Detail View, then to Compose Expense Detail, then to Notify Supervisor Detail.
  4. Confirm that Present Income Format → Send Income Format Tip and Present Expense Format → Send Expense Format Tip are wired for help messages.

Credential Required: Connect your Telegram credentials for Send Approval Outcome, Notify Supervisor Detail, Send Income Format Tip, and Send Expense Format Tip.

Step 6: Test and Activate Your Workflow

Validate message intake, logging, and approval callbacks before enabling the workflow in production.

  1. Click Execute Workflow and send a Telegram message to the bot to trigger Telegram Webhook Intake.
  2. Confirm the message passes through Identify Message Category → Direct by Input Kind → Process Start or Text and reaches Display Income Expense Menu or Verify Input Structure.
  3. Submit an income entry and verify Log Income to Sheet writes to your sheet and Confirm Income Logged returns a success message.
  4. Submit an expense entry and verify Log Expense to Sheet writes to your sheet and Alert Expense Pending → Dispatch Approval Prompt sends the approval request.
  5. Click an approval callback and ensure Modify Approval Status → Retrieve Approved Row → Send Approval Outcome completes the approval flow.
  6. When satisfied, toggle Active to enable the workflow for continuous use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Telegram credentials can fail if the bot token was regenerated. If messages stop arriving, check your n8n Telegram API credential and the BotFather token first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Google Sheets updates can silently miss the right row if your sheet structure changes. If approvals update the wrong line, check the “Modify Approval Status” mapping and confirm the correct spreadsheet tab name.

Related Workflows

If you like the idea of keeping everything in chat but don’t need approvals, Telegram to Google Sheets, expenses logged for you is a simpler baseline for fast capture.

For teams that live on photos and paper receipts, Telegram to Google Sheets, receipts logged for you pairs well because it focuses on getting receipt details into Sheets without manual typing.

When consistency is the real battle (same vendor spelled five ways, missing categories, messy notes), Telegram to Google Sheets, expenses logged clean helps tighten the “data hygiene” side so reports don’t become a cleanup project.

If expenses arrive from multiple places, not just Telegram, Gmail + Telegram to Google Sheets, expenses logged is handy for capturing email invoices and chat-based expenses into one sheet.

Finally, if you want the same logging habit but framed around monthly limits and calmer spending decisions, Telegram to Google Sheets, stress free budget tracking is a natural next step.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Telegram expense logging automation?

About 30 minutes if your Telegram bot and Google access are ready.

Do I need coding skills to automate Telegram expense logging?

No. You will mainly connect accounts and paste in IDs and tokens.

Is n8n free to use for this Telegram expense logging 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 Google Workspace access (if applicable), but this workflow doesn’t require paid AI calls to function.

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 expense logging workflow for multiple supervisors?

Yes, but you’ll want to adjust the “Dispatch Approval Prompt” logic to choose the right supervisor chatId based on category, team, or who submitted the expense. Many teams keep a simple mapping table in Google Sheets and look up the approver before sending the approval buttons.

Why is my Telegram connection failing in this workflow?

Usually it’s an invalid or replaced bot token, so n8n can’t authenticate to Telegram anymore. Update the Telegram API credential in n8n, then send /start to the bot again to confirm messages are arriving. If you run the bot in a group chat, privacy mode can also interfere with what the bot can “see,” so check your BotFather settings. And if approvals aren’t reaching the supervisor, verify the supervisor chatId in the node that sends the approval request.

How many transactions can this Telegram expense logging automation handle?

Plenty for most small teams: think hundreds of transactions a month without drama. On n8n Cloud, your limit depends on plan executions; if you self-host, it’s mostly your server size and Google Sheets API limits.

Is this Telegram expense logging automation better than using Zapier or Make?

Often, yes, because the approval flow needs branching, callbacks, and row updates that get awkward (and expensive) in simpler automation tools. n8n handles multi-path logic cleanly, and self-hosting is an option if you want unlimited runs. Zapier or Make can still work if you only want “Telegram message → add spreadsheet row” with no supervisor loop. This template’s value is the decision step, honestly. Talk to an automation expert if you want help choosing the simplest setup for your team.

Once this is running, expenses stop living in people’s heads and chat history. The workflow keeps the records clean, and your approvals stop being a scavenger hunt.

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.