Automation library · Integrations

Back up workflows to GitHub

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

Medium

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

The flow

Starts it 1Logic 4Service 5

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Get All Active WorkflowsN8nService
  3. 3Check if File exists And Return if ExistsGithubService
  4. 4Extract from FileExtract From FileService
  5. 5Check if File MissingIfLogic
  6. 6Check if Update to DateIfLogic
  7. 7Create a fileGithubService
  8. 8Ignores because it's not related to missing fileNo OpLogic
  9. 9Ignores Because it is already up to dateNo OpLogic
  10. 10Edit a fileGithubService

How it's built

Starts on
A clock
Steps
10, with 2 branches
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. 10 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 10 steps before you point it at anything that matters.