The flow
Starts it 1Logic 6Service 10
The steps in the order they run, from what starts it.
- 1Telegram TriggerTelegram triggerStarts it
- 2AddUserNoco DbService
- 3UpdateUserNoco DbService
- 4chatIDFunctionLogic
- 5MergeMergeLogic
- 6LoadDictionaryNoco DbService
- 7SwitchSwitchLogic
- 8botmessagesFunctionLogic
- 9New user?FunctionLogic
- 10msg_helpTelegramService
- 11msg_wrongcommandTelegramService
- 12CheckUserNoco DbService
- 13IFIfLogic
- 14HTTP AddUserHttp RequestService
- 15HTTP UpdateUserHttp RequestService
- 16msg_greetTelegramService
- 17msg_welcomebackTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 17, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- NocoDB, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own NocoDB 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. 17 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 17 steps before you point it at anything that matters.