The flow
Starts it 1Logic 6Service 8
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2SupabaseSupabaseService
- 3Microsoft SharePoint HTTP RequestHttp RequestService
- 4normalize last modified dateSetLogic
- 5filter filesCodeLogic
- 6Compare DatasetsCompare DatasetsService
- 7Supabase1SupabaseService
- 8Loop Over Items2Split In BatchesLogic
- 9get metadataCodeLogic
- 10Set metadataSetLogic
- 11Insert Document MetadataPostgresService
- 12Microsoft SharePoint HTTP Request1Http RequestService
- 13rename filesCodeLogic
- 14Upload fileGoogle DriveService
- 15PostgresPostgresService
How it's built
- Starts on
- A clock
- Steps
- 15, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, Postgres, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive, Postgres and Supabase 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. 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 itNothing 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.