Sync SharePoint to Google Drive via Supabase (n8n Workflow) — Workflow n8n

Moyen complexité⏰ Planifié15 nœuds🏷️ File Management👁 24 vuespar DIGITAL BIZ TECH

Aperçu

Eliminate manual file transfers and data silos with this enterprise-grade synchronization pipeline. This n8n workflow automates the heavy lifting of mirroring your Microsoft SharePoint document libraries to Google Drive while maintaining a robust audit trail in Supabase or Postgres. Designed for high-reliability environments, the automation utilizes a sophisticated delta-check logic: it fetches SharePoint metadata, compares it against your existing database records using the 'Compare Datasets' node, and identifies only new or modified files for processing.

By leveraging the 'Split in Batches' node, the system handles large volumes of data without hitting memory limits, ensuring every document is securely downloaded via HTTP and re-uploaded to its destination. Once the transfer is verified, the workflow updates your database status in real-time, providing a transparent log of your synchronization history. This is an essential solution for organizations transitioning between cloud ecosystems or those requiring a redundant, cross-platform backup strategy. It effectively bridges the gap between Microsoft and Google ecosystems using Supabase as a high-performance state-management layer.

💡

Common Use Cases

  • Automated Multi-Cloud Disaster Recovery: Maintain a real-time mirror of critical SharePoint corporate assets in Google Drive to ensure business continuity during service outages.
  • Cross-Departmental Collaboration: Automatically sync project documentation from an executive SharePoint site to a creative team's Google Drive folder for seamless cross-platform access.
  • Centralized Document Auditing: Use Supabase to track every file movement between ecosystems, creating a searchable metadata index for compliance and regulatory reporting.

Nœuds utilisés

HTTP RequestPostgresGoogle DriveSupabaseCode

Aperçu du workflow

SharePoint Sync Overview
How it works
Runs on a schedule, fetches SharePoint folders and file
Only new or modifi
extract metadata
Rename Files
Renames each downloaded binary file
with its corresponding SharePoint file title before upl
Postgres (Mark Complete)
Marks entries as processed by setting `Loading Done = t
once uploads are complete.
Upload file (Google Drive)
Uploads downloaded files to Google Drive for safe stora
Microsoft SharePoint HTTP Request1 (Download)
Downloads each new or updated file directly from ShareP
Insert Document Metadata
Upserts processed SharePoint file data into `n8n_metada
Creates or updates existing records.
delete file from supabase (metadata table)
Filter Files
Filters out system and temporary files (`~$`, `.db`, `.
and flattens nested folders into a single clean file li
Compare Datasets
Compares SharePoint and Supabase data
to detect new or updated files and flag records for pro
Microsoft SharePoint HTTP Request
Retrieves all folders and files recursively from the sp
Supabase (Get)
Retrieves existing records from `n8n_metadata`
to check which SharePoint files are already stored.
Schedule Trigger
Triggers the workflow on a defined schedule
standardizes
`Last_modified_date`
loop over newly added or modified files
L
Loop Over Items2
Microsoft SharePoint HTT…
⚡
S
Schedule Trigger
C
Compare Datasets
Supabase
Supabase1
Insert Document Metadata
Postgres
Upload file
Microsoft SharePoint HTT…
filter files
N
normalize last modified …
get metadata
S
Set metadata
rename files
15 nodes17 edges

Comment ça fonctionne

  1. 1

    Déclencheur

    Le workflow démarre avec un déclencheur planifié, s'exécutant selon un planning défini.

  2. 2

    Traitement

    Les données transitent par 15 nœuds, connecting code, comparedatasets, googledrive.

  3. 3

    Sortie

    Le workflow termine son automatisation et livre le résultat à la destination configurée.

Détails des nœuds (15)

HT

HTTP Request

httpRequest

#1
PO

Postgres

postgres

#2
GO

Google Drive

googleDrive

#3
SU

Supabase

supabase

#4
CO

Code

code

#5

Comment importer ce workflow

  1. 1Cliquez sur le bouton Télécharger JSON à droite pour enregistrer le fichier du workflow.
  2. 2Ouvrez votre instance n8n. Accédez à Workflows → Nouveau → Importer depuis un fichier.
  3. 3Sélectionnez le fichier automated-document-sync-between-sharepoint-and-google-drive-with-supabase téléchargé et cliquez sur Importer.
  4. 4Configurez les identifiants pour chaque nœud de service (clés API, OAuth, etc.).
  5. 5Cliquez sur Tester le workflow pour vérifier que tout fonctionne, puis activez-le.

Ou collez directement dans n8n → Importer depuis JSON :

{ "name": "Sync SharePoint to Google Drive via Supabase (n8n Workflow)", "nodes": [...], ...}

Intégrations

codecomparedatasetsgoogledrivehttprequestpostgresscheduletriggersetsplitinbatchessupabase

Obtenir ce workflow

Téléchargez et importez en un clic

Télécharger JSONVoir sur n8n.io
Nœuds15
Complexitémedium
Déclencheurscheduled
Vues24
CatégorieFile Management

Créé par

DIGITAL BIZ TECH

DIGITAL BIZ TECH

@dbt

Tags

codecomparedatasetsgoogledrivehttprequestpostgresscheduletriggersetsplitinbatchessupabase
⚡

Nouveau sur n8n ?

n8n est un outil d'automatisation de workflows gratuit et open-source. Hébergez-le vous-même ou utilisez la version cloud.

Obtenir n8n gratuitement →

Related File Management Workflows

FOGOGOHT+2
medium

Automate Threads Video Backups to Google Drive & Sheets

Streamline your social media asset management with this robust n8n automation designed for digital marketers and content creators. This workflow eliminates the manual effort of downloading Threads content by providing a seamless bridge between Instagram's text-based platform and your cloud storage. Once triggered via a simple form input, the automation utilizes a RapidAPI connection to fetch high-quality video assets, processes the binary data, and securely uploads the file to a designated Google Drive folder. Simultaneously, the workflow maintains a centralized audit log in Google Sheets, capturing essential metadata such as timestamps and file IDs. Built-in logic gates and wait nodes ensure API rate limits are respected and file transfers are verified before logging. This is an essential tool for agencies managing high volumes of social content who need a reliable, automated pipeline for content repurposing, archival compliance, or collaborative review processes. By centralizing your Threads media assets, you ensure your creative team has instant access to raw footage without the friction of manual downloads. **Common Use Cases:** - Automated Social Media Content Archiving for Compliance - Centralized Asset Library Syncing for Creative Agencies - Competitor Research and Video Content Benchmarking

⚡ Trigger·9 nodes