Automation library · Chat assistants
Started by an incoming Telegram message, and works across Supabase and Telegram. It puts OpenRouter behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 8 steps, 1 branch: small enough to read in one sitting and change without fear.
Starts it 1Model 3Logic 1Service 3
The steps in the order they run, from what starts it.
An n8n account, plus your own Supabase and Telegram accounts, 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.
Not long. At 8 steps it can be read in one sitting and changed without fear.
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 8 steps before you point it at anything that matters.