Automation library · Alerts and monitoring

Automated workflow backups with Google Drive and Slack

Started by a clock, and works across Google Drive and Slack. 12 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 3Service 7

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

  1. 1On clicking 'execute'Manual triggerStarts it
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3create new folderGoogle DriveService
  4. 4Set New Folder IdSetLogic
  5. 5Get many workflowsN8nService
  6. 6Failed NotificationSlackService
  7. 7MergeMergeLogic
  8. 8Convert to File1Convert To FileService
  9. 9Upload fileGoogle DriveService
  10. 10CodeCodeLogic
  11. 11Completed NotificationSlackService
  12. 12CompressionCompressionService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Google Drive 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. 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.