Automation library · Alerts and monitoring

Scheduled Google Drive monitoring with Postgres

Started by a clock, and works across Google Drive and Postgres. 13 steps, 2 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

Download free
13 stepsMedium: a working afternoon
2Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 9Service 3

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Find Files In FolderGoogle DriveService
  3. 3Normalize DataCodeLogic
  4. 4Get Tracked File DataPostgresService
  5. 5Evaluate EditsCodeLogic
  6. 6Loop Over Items1Split In BatchesLogic
  7. 7Merge after Processing CompleteMergeLogic
  8. 8Check File OperationSwitchLogic
  9. 9IfIfLogic
  10. 10File Added ProcessingNo OpLogic
  11. 11File Modified ProcessingNo OpLogic
  12. 12File Deleted ProcessingNo OpLogic
  13. 13Update File MetadataPostgresService

How it's built

Starts on
A clock
Steps
13, with 2 branches, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Google Drive, Postgres
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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