Automation library · Documents and files

Process large documents with OCR and SubworkflowAI

Started by an event in a connected app, and works across Google Drive. It hands the judgement calls to Gemini. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

MediumCalls a model: Gemini

10 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Model 1Logic 3Service 5

The steps in the order they run, from what starts it.

  1. 1When clicking ‘Execute workflow’Manual triggerStarts it
  2. 2Download fileGoogle DriveService
  3. 3Extract APIHttp RequestService
  4. 4Job Complete?IfLogic
  5. 5Get DatasetHttp RequestService
  6. 6Check Job StatusHttp RequestService
  7. 7Get Dataset ItemsHttp RequestService
  8. 8WaitWaitLogic
  9. 9Split OutSplit OutLogic
  10. 10Document OCR via VLMGoogle GeminiModel

How it's built

Starts on
An event in a connected app
Steps
10, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Google Drive
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Google Drive account, and a key for Gemini. 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?

Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 10 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 it

Nothing 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 10 steps before you point it at anything that matters.