Automation library · Alerts and monitoring

Automated n8n workflow backup with Telegram

Started by a clock, and works across Telegram. 11 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 2Service 7

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

  1. 1Каждые 3 часаSchedule triggerStarts it
  2. 2On clicking 'execute'Manual triggerStarts it
  3. 3CodeCodeLogic
  4. 4Старт бэкапаTelegramService
  5. 5Get many workflowsN8nService
  6. 6Loop Over ItemsSplit In BatchesLogic
  7. 7Считаем кол-воSummarizeService
  8. 8Completed Notification1TelegramService
  9. 9Convert to FileConvert To FileService
  10. 10Send a text message1TelegramService
  11. 11Отправляем файлыTelegramService

How it's built

Starts on
A clock
Steps
11, 1 loop or waits
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 a clock.

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. 11 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 11 steps before you point it at anything that matters.