Route rental payment and receipt messages with Telegram and OpenAI GPT-4.1
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 AI workflow has 22 nodes and runs on Telegram events (message). Along the way it connects Telegram and OpenAI.
How it runs
Trigger: On Telegram events (message).
- Route Telegram Message (Code): runs custom JavaScript code
- Is Full Receipt Command? (If): checks a condition and branches into true / false
- Receipt Parse Message (Code): runs custom JavaScript code
- Is Receipt Request? (If): checks a condition and branches into true / false
- Demo Full Receipt Parsed Reply (Telegram): uses Telegram
- Get Last Payment For Receipt (Code): runs custom JavaScript code
- Is Receipt Date Reply? (If): checks a condition and branches into true / false
- Has Last Payment? (If): checks a condition and branches into true / false
- Build Receipt From Pending Payment (Code): runs custom JavaScript code
- Tracker Prepare Telegram Text (Code): runs custom JavaScript code
…plus 11 more steps. See the full node list below.
Services it uses
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 (5)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - OpenAI
@n8n/n8n-nodes-langchain.openAi
From the author
Quick overview This demo workflow listens for Telegram rental messages, routes receipt-related commands, uses OpenAI to classify payments, costs, and booking summaries, then replies with parsed details and a sample receipt flow. How it works 1. Triggers when…