Automation library · Documents and files

Backup workflow & credentials to Cloudflare R2 with S3

Started by a clock, and works across S3 and Slack. 10 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 1Service 7

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

  1. 1On clicking 'execute'Manual triggerStarts it
  2. 2CronCronStarts it
  3. 3Date & TimeDate TimeLogic
  4. 4Export WorkflowsExecute CommandService
  5. 5Export CredentialsExecute CommandService
  6. 6Read/Write Files from DiskRead Write FileService
  7. 7Read/Write Files from Disk1Read Write FileService
  8. 8S3S3Service
  9. 9S31S3Service
  10. 10SlackSlackService

How it's built

Starts on
A clock
Steps
10
Size
Medium: a working afternoon
Connects to
S3, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own S3 and Slack 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. 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.