workflows.fit
Back to n8n workflows
n8n templateFreeBy Shashwat Singh

Detect and move duplicate Google Drive files with Supabase and Slack

This workflow automatically detects duplicate files uploaded to a specific Google Drive folder by generating an MD5 hash of each file and comparing it against a Supabase database. If a duplicate is found, the file is ...

CommunicationHITLData & StorageDevelopmentCore NodesGoogle Drive TriggerCodeGoogle Drive
Loading interactive preview...

Template notes

This workflow automatically detects duplicate files uploaded to a specific Google Drive folder by generating an MD5 hash of each file and comparing it against a Supabase database. If a duplicate is found, the file is moved to a dedicated Duplicates folder and a Slack notification is sent. All events, including unique uploads, duplicates, race conditions, and errors, are logged for audit purposes.

It is designed for teams that handle high file volumes and need reliable, content based deduplication instead of simple filename checks.

How it works

- Monitors a specific Google Drive folder for new files.

- Normalizes file metadata and downloads the binary content. - Generates an MD5 hash from the file binary.

- Checks Supabase to see if the hash already exists.

- If duplicate, moves the file to a Duplicates folder and sends a Slack alert.

- If unique, stores the hash in Supabase.