Automation library · Documents and files

Backup workflows to GitHub

Started by a clock, and works across GitHub. 11 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 4Service 6

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

  1. 1Get FilesGithubService
  2. 2Daily at 23:59CronStarts it
  3. 3TransformFunctionLogic
  4. 4Get workflowsHttp RequestService
  5. 5Download Raw ContentHttp RequestService
  6. 6transformFunctionLogic
  7. 7MergeMergeLogic
  8. 8Merge1MergeLogic
  9. 9Get workflow dataHttp RequestService
  10. 10Create fileGithubService
  11. 11GitHub EditGithubService

How it's built

Starts on
A clock
Steps
11
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. 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.