The flow
Starts it 1Logic 6Service 6
The steps in the order they run, from what starts it.
- 1Receive Invoice On TelegramTelegram triggerStarts it
- 2ConfigSetLogic
- 3Validate Sender And Detect File TypeCodeLogic
- 4Is File Supported?IfLogic
- 5Download Invoice From TelegramTelegramService
- 6Reply Unsupported MessageTelegramService
- 7Build Claude RequestCodeLogic
- 8Extract Invoice With ClaudeHttp RequestService
- 9Parse Claude ResponseCodeLogic
- 10Create Gmail Draft For AccountantGmailService
- 11Archive Invoice To Google DriveGoogle DriveService
- 12Merge Draft And ArchiveMergeLogic
- 13Send Telegram ConfirmationTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 13, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Drive, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Drive and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an incoming Telegram message.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 13 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.