Automation library · Content

Daily Postgres table backup to GitHub in CSV format

Started by a clock, and works across GitHub and Postgres. 12 steps, 1 branch, 2 loops or waits: a working afternoon to understand properly.

Medium

Download free
12 stepsMedium: a working afternoon
1Branch: places the flow splits
2Loops or waits
2Services it connects to

The flow

Starts it 1Logic 5Service 6

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

  1. 1Daily ScheduleSchedule triggerStarts it
  2. 2List files from repository [GITHUB]GithubService
  3. 3Combine file names [GITHUB]Item ListsLogic
  4. 4List tables1PostgresService
  5. 5Loop Over ItemsSplit In BatchesLogic
  6. 6Split to single itemsSplit In BatchesLogic
  7. 7CodeCodeLogic
  8. 8Check if file exists in repositoryIfLogic
  9. 9List tablesPostgresService
  10. 10Update file [GITHUB]GithubService
  11. 11Upload file [GITHUB]GithubService
  12. 12Convert to File1Convert To FileService

How it's built

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

Questions

What does it need to run?

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