Automation library · Documents and files

n8n backup flow to Nextcloud

Started by a clock. It calls services over plain HTTP rather than through connectors. 12 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
0Branches: places the flow splits
1Loop or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 5Service 5

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

  1. 1On clicking 'execute'Manual triggerStarts it
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3Backup PathSetLogic
  4. 4Nextcloud DirectoryNext CloudService
  5. 5n8nN8nService
  6. 6Loop Over ItemsSplit In BatchesLogic
  7. 7Nextcloud List DirNext CloudService
  8. 8CodeCodeLogic
  9. 9BackupsSortLogic
  10. 10Nextcloud UploadNext CloudService
  11. 11Limits BackupsCodeLogic
  12. 12Nextcloud - Delete old backupsNext CloudService

How it's built

Starts on
A clock
Steps
12, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n 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. 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.