The flow
Starts it 1Logic 11Service 9
The steps in the order they run, from what starts it.
- 1Google Drive TriggerGoogle Drive triggerStarts it
- 2Prepare File InfoCodeLogic
- 3Download FileGoogle DriveService
- 4Validate BinaryIfLogic
- 5CryptoCryptoService
- 6Handle Missing BinaryCodeLogic
- 7Check Hash ExistsSupabaseService
- 8Prepare Error Log DataCodeLogic
- 9Same File Re-triggered?IfLogic
- 10Log Error EventSupabaseService
- 11No Operation, do nothingNo OpLogic
- 12Hash Matched Different File?IfLogic
- 13Move to DuplicatesGoogle DriveService
- 14Prepare Hash DataCodeLogic
- 15Notify DuplicateSlackService
- 16Insert New HashSupabaseService
- 17Prepare Dup Log DataCodeLogic
- 18Handle DB ErrorCodeLogic
- 19Log Duplicate EventSupabaseService
- 20Prepare Unique Log DataCodeLogic
- 21Log Unique EventSupabaseService
How it's built
- Starts on
- An event in a connected app
- Steps
- 21, with 3 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Google Drive, Slack, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive, Slack and Supabase accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
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 21 steps before you point it at anything that matters.