Automation library · Alerts and monitoring

Monitor and download changed files from Google Drive

Started by a clock, and works across Google Drive. 15 steps, 1 branch: a working afternoon to understand properly.

Medium

15 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 7Service 7

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

  1. 1Schedule Trigger1Schedule triggerStarts it
  2. 2Search for Timestamp File1Google DriveService
  3. 3Download Timestamp File1Google DriveService
  4. 4Extract Timestamp Text1Extract From FileService
  5. 5Edit Fields2SetLogic
  6. 6Search for New Files2Google DriveService
  7. 7IfIfLogic
  8. 8Download New Files2Google DriveService
  9. 9No OperationNo OpLogic
  10. 10MergeMergeLogic
  11. 11Edit FieldsSetLogic
  12. 12Delete Old Timestamp File1Google DriveService
  13. 13Get Current Time1Date TimeLogic
  14. 14Create Timestamp FileCodeLogic
  15. 15Upload New Timestamp2Google DriveService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Google Drive 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. 15 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 15 steps before you point it at anything that matters.