Automation library · Scheduling

Back up all workflows to GitHub with Telegram

Started by an incoming Telegram message, and works across GitHub and Telegram. 9 steps: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 2Service 5

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

  1. 1When Daily at 3 AMSchedule triggerStarts it
  2. 2Telegram /backup Command TriggerTelegram triggerStarts it
  3. 3Fetch All WorkflowsN8nService
  4. 4Filter for Backup CommandFilterLogic
  5. 5Build Backup FileCodeLogic
  6. 6Check File Existence in GitHubGithubService
  7. 7Update File on GitHubGithubService
  8. 8Create File on GitHubGithubService
  9. 9Notify via TelegramTelegramService

How it's built

Starts on
An incoming Telegram message
Steps
9
Size
Medium: a working afternoon
Connects to
GitHub, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub 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. 9 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 9 steps before you point it at anything that matters.