The flow
Starts it 1Logic 12Service 7
The steps in the order they run, from what starts it.
- 1Google Drive TriggerGoogle Drive triggerStarts it
- 2Download FileGoogle DriveService
- 3Build MetadataCodeLogic
- 4Check CacheSupabaseService
- 5Merge Metadata + JobMergeLogic
- 6Debug Cache ResultsCodeLogic
- 7Init Loop StateCodeLogic
- 8If Cache ExistsIfLogic
- 9wait till interval set timeWaitLogic
- 10STOP, CachedCodeLogic
- 11Submit to Landing.aiHttp RequestService
- 12Poll Job StatusHttp RequestService
- 13If CompletedIfLogic
- 14check-large-fileIfLogic
- 15If TimeoutIfLogic
- 16HTTP Request1Http RequestService
- 17Save Parse ResultSupabaseService
- 18Log TimeoutSupabaseService
- 19STOP, SuccessCodeLogic
- 20STOP, TimeoutCodeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 20, with 4 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive 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?
Plan an afternoon. 20 steps is enough that you should read each one before running it.
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 20 steps before you point it at anything that matters.