Automation library · Scheduling
Started by an incoming Telegram message, and works across Telegram. It puts OpenRouter behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 12 steps: a working afternoon to understand properly.
Starts it 1Model 9Service 2
The steps in the order they run, from what starts it.
An n8n account, plus your own Telegram account, and a key for OpenRouter. You connect your own accounts after importing it; none are included.
It starts on an incoming Telegram message.
Yes. It calls OpenRouter. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.
Plan an afternoon. 12 steps is enough that you should read each one before running 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 12 steps before you point it at anything that matters.