Automated document sync between SharePoint and Google Drive with Supabase
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 15 nodes and runs on a schedule (every day). Along the way it connects Supabase, Postgres and Google Drive.
How it runs
Trigger: On a schedule (every day).
- Supabase: get many
- Microsoft SharePoint HTTP Request (HTTP Request): calls an HTTP API (GET)
- normalize last modified date (Edit Fields (Set)): sets 1 field: Last_modified_date
- filter files (Code): runs custom JavaScript code
- Compare Datasets: uses Compare Datasets
- Supabase: delete
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- get metadata (Code): runs custom JavaScript code
- Set metadata (Edit Fields (Set)): sets 7 fields: file_id, file_type, file_title…
- Insert Document Metadata (Postgres): create or update
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Compare Datasets
n8n-nodes-base.compareDatasets - Supabase
n8n-nodes-base.supabase - Postgres
n8n-nodes-base.postgres - Google Drive
n8n-nodes-base.googleDrive - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set
From the author
SharePoint → Supabase → Google Drive Sync Workflow Overview This workflow is a multi-system document synchronization pipeline built in n8n, designed to automatically sync and back up files between Microsoft SharePoint, Supabase/Postgres, and Google Drive. It…