Automation library · Documents and files

Workflow automate GitHub backups

Started by a clock, and works across GitHub. 14 steps, 2 branches, 2 loops or waits: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 6Service 7

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Execute CommandExecute CommandService
  3. 3ExportarWorkflowsExecute CommandService
  4. 4Read Binary FilesRead Binary FilesService
  5. 5Move Binary DataMove Binary DataService
  6. 6Loop Over ItemsSplit In BatchesLogic
  7. 7No Operation, do nothingNo OpLogic
  8. 8WaitWaitLogic
  9. 9WorkflowSetLogic
  10. 10GitHubWorkflowGithubService
  11. 11IFIfLogic
  12. 12GitHub2GithubService
  13. 13Convert to/from binary dataMove Binary DataService
  14. 14IF1IfLogic

How it's built

Starts on
A clock
Steps
14, with 2 branches, 2 loops or waits
Size
Medium: a working afternoon
Connects to
GitHub
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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