Construction blueprint to Google Sheets automation with VLM Run and Google Drive
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 4 nodes and runs on Google Drive events (file created). Along the way it connects Google Sheets, Google Drive and Vlmrun (community).
How it runs
Trigger: On Google Drive events (file created).
- Download file (Google Drive): download
- Vlm Run: uses Vlm Run
- Append row in sheet (Google Sheets): append
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @vlm-run/n8n-nodes-vlmrun is verified or supports 3.0 (used in VLM Run).
Nodes used (4)
- Vlm Run
@vlm-run/n8n-nodes-vlmrun.vlmRun - Google Sheets
n8n-nodes-base.googleSheets - Google Drive
n8n-nodes-base.googleDrive - Google Drive Trigger
n8n-nodes-base.googleDriveTrigger
From the author
Automatically process Construction Blueprints into structured Google Sheets entries with VLM extraction What this workflow does 1. Monitors Google Drive for new blueprints in a target folder 2. Downloads the file inside n8n for processing 3. Sends the file to…