Detect and move duplicate Google Drive files with Supabase and Slack
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 21 nodes and runs on Google Drive events (file created). Along the way it connects Google Drive, Supabase and Slack.
How it runs
Trigger: On Google Drive events (file created).
- Prepare File Info (Code): runs custom JavaScript code
- Download File (Google Drive): download
- Validate Binary (If): checks a condition and branches into true / false
- Crypto: hashes or encrypts values
- Handle Missing Binary (Code): runs custom JavaScript code
- Check Hash Exists (Supabase): get many
- Prepare Error Log Data (Code): runs custom JavaScript code
- Same File Re-triggered? (If): checks a condition and branches into true / false
- Log Error Event (Supabase): uses Supabase
- Hash Matched Different File? (If): checks a condition and branches into true / false
…plus 9 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 (8)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Code
n8n-nodes-base.code - Google Drive
n8n-nodes-base.googleDrive - If
n8n-nodes-base.if - Crypto
n8n-nodes-base.crypto - Supabase
n8n-nodes-base.supabase - Slack
n8n-nodes-base.slack - No Operation, do nothing
n8n-nodes-base.noOp
From the author
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…