Automation library · Alerts and monitoring

Automated Telegram UserBot session monitoring & recovery

Started by someone opening a chat with it, and works across Telegram. 13 steps: a working afternoon to understand properly.

Medium

13 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Logic 5Service 6

The steps in the order they run, from what starts it.

  1. 1When chat message receivedChat triggerStarts it
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3Manual controlTele PilotService
  4. 4Get Session StatusSetLogic
  5. 5Automatic controlTele PilotService
  6. 6Pass on Closed StatusFilterLogic
  7. 7Send Closed Status messageTelegramService
  8. 8Stop SessionSetLogic
  9. 9Stop authTele PilotService
  10. 10Start SessionSetLogic
  11. 11Start authTele PilotService
  12. 12Check Session ConnectionFilterLogic
  13. 13Send Session Connection messageTelegramService

How it's built

Starts on
Someone opening a chat with it
Steps
13
Size
Medium: a working afternoon
Connects to
Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Telegram account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone opening a chat with it.

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.

Before you run it

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.