Parse Google Drive documents to RAG-ready Markdown with Landing.ai and Supabase cache
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 workflow has 20 nodes and runs on Google Drive events (file created). Along the way it connects Google Drive and Supabase. It also calls api.va.landing.ai over HTTP.
How it runs
Trigger: On Google Drive events (file created).
- Download File (Google Drive): download
- Build Metadata (Code): runs custom JavaScript code
- Check Cache (Supabase): get many
- Merge: merges the data from its input branches
- Debug Cache Results (Code): runs custom JavaScript code
- Init Loop State (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Wait: pauses before continuing
- STOP — Cached (Code): runs custom JavaScript code
- Submit to Landing.ai (HTTP Request): calls api.va.landing.ai (POST)
…plus 9 more steps. See the full node list below.
Services it uses
HTTP calls to: api.va.landing.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 (8)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Google Drive
n8n-nodes-base.googleDrive - Code
n8n-nodes-base.code - Supabase
n8n-nodes-base.supabase - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Wait
n8n-nodes-base.wait
From the author
Make your unstructured large documents LLM ready markdown using LandingAI Document Parsing. - Automatically watches a Google Drive folder, submits new documents to Landing.ai for parsing, caches processed files in - Supabase to avoid reprocessing, and…