Automated expense tracking with Telegram, easybits & Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 24 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Telegram. It also calls api.telegram.org, extractor.easybits.tech and sheets.googleapis.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Has Photo or PDF? (If): checks a condition and branches into true / false
- Get File Info (HTTP Request): calls an HTTP API (POST)
- No Photo Message (HTTP Request): calls api.telegram.org (POST)
- Download Photo (HTTP Request): calls an HTTP API
- Respond OK (Respond to Webhook): sends the response back to the webhook caller
- Convert to Base (Code): runs custom JavaScript code
- Extract with easybits (HTTP Request): calls extractor.easybits.tech (POST)
- Process Extraction (Code): runs custom JavaScript code
- Needs Category? (If): checks a condition and branches into true / false
- Ask for Category (Telegram): uses Telegram
…plus 13 more steps. See the full node list below.
Services it uses
HTTP calls to: api.telegram.org, extractor.easybits.tech, sheets.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook - Telegram
n8n-nodes-base.telegram
From the author
How it works I wanted to avoid the rush at end of month to log expenses. I tried existing expense apps but found them either too expensive for what they offer, or frustrating with inconsistent extraction results. That is why I built my own Telegram expense…