How to Connect n8n to Google Drive: The Complete Integration Guide (2025)
Google Drive is where most businesses keep their documents, contracts, invoices, and exports — and moving files around it by hand is a quiet time sink. n8n turns Drive into an active part of your workflows: watch a folder for new files, process them the instant they arrive, upload generated reports, and keep everything organized without lifting a finger. Here's the complete setup.
What n8n + Google Drive unlocks
Once connected, Drive can be both a trigger and a destination. Teams use it to process invoices dropped into a folder, back up data on a schedule, auto-organize incoming files by type, generate and store PDF reports, and feed documents into AI pipelines for summarization or extraction. If a file touches your business, n8n can act on it.
Step 1 — Set up Google OAuth credentials
Google Drive uses OAuth2. In the Google Cloud Console, create a project, enable the Google Drive API, and configure the OAuth consent screen. Then create an OAuth client ID of type Web application and add n8n's redirect URL (shown in the n8n credential screen) to the authorized redirects. Copy the client ID and secret into n8n.
Step 2 — Authorize the connection
Back in n8n, create a Google Drive OAuth2 API credential, paste your client ID and secret, and click Connect my account. A Google popup asks you to sign in and grant Drive access. Approve it, and n8n stores the refresh token so the connection stays alive without re-authenticating.
⚡ Skip the build — get the ready-made template
Want to do more than move files? This template turns your Google Drive folder into a searchable AI chatbot that answers questions from your documents.
Get "RAG Chatbot on Google Drive Docs — Gemini + Qdrant + Telegram" on Gumroad →
Step 3 — Watch a folder for new files
The Google Drive Trigger node fires whenever a file is created or updated in a folder you select. This is the backbone of document automations: drop a receipt into a folder and n8n immediately extracts the data, or add a contract and it gets summarized and filed. Set the poll interval as low as one minute for near-real-time processing.
Step 4 — Upload, download, and move files
The Google Drive node handles the full lifecycle: Upload a file (including binary data generated earlier in the workflow), Download to pass a file into another node, Move or Copy between folders, and Share with specific permissions. A common pattern is generate-a-PDF → upload-to-Drive → share-link-in-Slack, all in one flow.
Step 5 — Work with binary data correctly
Files in n8n travel as binary data attached to items. When you download from Drive, the file lives in the binary property; when you upload, you point the node at that property. If you're converting a document — say generating a PDF from HTML — make sure the binary property names line up between nodes, since a mismatch is the number-one reason uploads come out empty.
A real example: invoices to structured data
Drop invoices into a Drive folder, let the trigger catch each one, pass it to an AI extraction node, write the parsed fields to Google Sheets, and archive the original to a 'processed' folder. That single workflow eliminates manual data entry for accounts payable — and Drive is the reliable front door for the whole thing.
Troubleshooting
If authorization fails, double-check the redirect URL matches exactly and that the Drive API is enabled in your Cloud project. If the trigger misses files, confirm you selected the right folder and that the polling account has access to it. For shared drives, make sure the OAuth account is a member — personal permissions don't automatically extend to team drives.
Ready to automate? Get this template on Gumroad →
Import the JSON, plug in your credentials, and it runs in minutes.
