Process large documents with OCR using SubworkflowAI and Gemini
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 AI workflow has 10 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Drive and Google Gemini. It also calls api.subworkflow.ai over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Download file (Google Drive): download
- Extract API (HTTP Request): calls api.subworkflow.ai (POST)
- Job Complete? (If): checks a condition and branches into true / false
- Get Dataset (HTTP Request): calls an HTTP API
- Check Job Status (HTTP Request): calls an HTTP API
- Get Dataset Items (HTTP Request): calls an HTTP API
- Wait: waits 1 seconds
- Split Out: splits a list into separate items
- Document OCR via VLM (Google Gemini): analyze (image)
Services it uses
HTTP calls to: api.subworkflow.ai
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 (7)
- Wait
n8n-nodes-base.wait - HTTP Request
n8n-nodes-base.httpRequest - Manual Trigger
n8n-nodes-base.manualTrigger - Google Drive
n8n-nodes-base.googleDrive - Split Out
n8n-nodes-base.splitOut - If
n8n-nodes-base.if - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini
From the author
Working with Large Documents In Your VLM OCR Workflow Document workflows are popular ways to use AI but what happens when your document is too large for your app or your AI to handle? Whether its context window or application memory that's grinding to a halt,…