The flow
Starts it 2Logic 5Service 9
The steps in the order they run, from what starts it.
- 1Start (mock data)Manual triggerStarts it
- 2Cron Job (5 mins)Schedule triggerStarts it
- 3Convert to batch requests in .jsonlCodeLogic
- 4Get the earliest uncompleted batchPostgresService
- 5Call Files APIHttp RequestService
- 6Call Batch API to retrieve batch objectHttp RequestService
- 7Call Batch APIHttp RequestService
- 8If status = completedIfLogic
- 9Create a row in batch tableSupabaseService
- 10Download .jsonl resultHttp RequestService
- 11Update statusSupabaseService
- 12Submission doneNo OpLogic
- 13.jsonl to base64Extract From FileService
- 14Decode base64CodeLogic
- 15Update status and resultSupabaseService
- 16Retrieval doneNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Postgres, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Postgres and Supabase accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 16 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 16 steps before you point it at anything that matters.