How to Connect Google Drive to n8n: Full 2026 Integration Guide

You need four things to connect Google Drive to n8n: a Google Cloud project with the Drive API enabled, OAuth 2.0 credentials (Client ID + Client Secret), a correctly configured redirect URI, and the proper OAuth scopes. The entire setup takes 15–20 minutes. The most common failure point is a redirect_uri_mismatch caused by a single character difference between what Google Cloud expects and what n8n sends. Fix that first.

“The OAuth consent screen is where 80% of users get stuck not because it is hard, but because Google hides the test-user requirement behind a scroll. Scroll down, add yourself, or you will see ‘access denied’ forever.”

n8n Google Drive Integration: What You Can Automate

n8n’s native Google Drive node (version included in all n8n 1.x and 2.x releases as of 2026) supports the following operations out of the box:

Operation	Supported Actions	Typical Use Case
File Operations	Upload, Download, Copy, Move, Update, Delete, Share	Automated document processing pipelines
Folder Operations	Create, List, Delete	Organizing user-generated content into dated folders
Shared Drive Operations	List, Get metadata	Team-wide file governance dashboards
Search	Query by name, MIME type, parent folder, trashed=false	Audit workflows, compliance scans
Trigger (Watch)	File Created, File Modified, File Deleted	Real-time event-driven automation

The Google Drive Trigger node (named n8n-nodes-base.googleDriveTrigger) polls a specified folder at a configurable interval. When a change event fires, it outputs the file’s ID, name, MIME type, size, and parent folder available as $json data for every downstream node.

Bolded definitions you will encounter throughout this guide:

OAuth 2.0 The industry-standard authorization framework that lets n8n access Google Drive on your behalf without ever seeing your Google password. It uses short-lived access tokens and long-lived refresh tokens.

Redirect URI The URL Google Cloud sends the user back to after they approve access. For self-hosted n8n, this is http://localhost:5678/rest/oauth2-credential/callback. For n8n Cloud instances, it uses the cloud provider’s callback endpoint.

OAuth Scope A permission string (e.g., https://www.googleapis.com/auth/drive) that defines exactly what operations n8n can perform on your Drive files. Scopes are presented to the user on the consent screen.

Managed OAuth2 A 2026 n8n Cloud feature where n8n itself handles the OAuth handshake using pre-verified Google credentials, eliminating the need for you to create your own Google Cloud project.

2026 Setup Decision: Managed OAuth2 vs. Custom OAuth2

Before you open Google Cloud Console, determine which authentication path applies to you:

Factor	Managed OAuth2 (n8n Cloud)	Custom OAuth2 (Self-Hosted)
Requires Google Cloud project	No	Yes
Requires OAuth consent screen	No	Yes
Requires Client ID/Secret creation	No	Yes
Google app verification needed	No (n8n handles it)	Yes, unless using test users
Setup time	~2 minutes per node	~15 minutes first time, ~5 minutes subsequent
Available for	Google Drive, Gmail, Sheets, Calendar, Docs, Slides	All Google services with OAuth2 API credentials
Portability	Tied to n8n Cloud account	Works on any n8n instance

If you are on n8n Cloud, check whether Managed OAuth2 is enabled for the Google Drive node in your region before proceeding. If it is available, skip directly to Step 4 below and choose “OAuth2 (n8n-managed)” when creating credentials.

If you are self-hosting n8n (Docker, npm, Kubernetes, or bare metal), continue with the Custom OAuth2 path below.

Step 1: Create a Google Cloud Project and Enable the Drive API

1. Navigate to console.cloud.google.com.
2. Click the project dropdown at the top navigation bar, then click New Project.
3. Name it n8n-Drive-Integration (the name only matters for your own organization).
4. Select a billing account. The Google Drive API is free for standard usage; a billing account is required but you will not incur charges unless you exceed the quota of 10,000,000 requests per day.
5. Click Create and wait ~10 seconds for the project to initialize.
6. With the new project selected, open the left-side navigation menu > APIs & Services > Library.
7. Search for Google Drive API. Select the result (not “Google Drive Activity API”).
8. Click Enable.

The API enablement grants the project permission to make calls to Google Drive. Without this toggle, even perfectly configured credentials will return HTTP 403 errors.

Step 2: Configure the OAuth Consent Screen

The consent screen is what users see when they authorize your integration. Even if the only user is you, it must be configured.

1. From APIs & Services > OAuth consent screen.
2. Choose External as the User Type. (Internal is available only to Google Workspace organizations.)
3. Click Create.
4. Fill in the required fields:
   • App name: n8n Drive Connector (this appears on the consent screen)
   • User support email: Your email address
   • Developer contact information: Your email address
5. Click Save and Continue.
6. On the Scopes screen, click Add or Remove Scopes. Search for and select:
   • https://www.googleapis.com/auth/drive (full Drive access recommended for maximum flexibility)
   • https://www.googleapis.com/auth/drive.file (access only to files created by this app)
   • https://www.googleapis.com/auth/drive.readonly (read-only, if write access is unnecessary)
   • https://www.googleapis.com/auth/spreadsheets (if your workflows involve Google Sheets)
7. Click Update, then Save and Continue.
8. On the Test users screen, click Add Users and enter your Google email address. This step is critical. Without it, an unverified “External” app will reject every authorization attempt, displaying “Access denied: App is not verified.”
9. Click Save and Continue, then review the summary.

You may also publish the app (under Audience > Publish App). Publishing removes the unverified-app warning banner during authorization but requires Google’s verification process for production apps. For development and internal use, test users suffice.

Step 3: Create OAuth 2.0 Credentials

1. Go to APIs & Services > Credentials.

2. Click Create Credentials > OAuth client ID.

3. Set Application type to Web application.

4. Name it n8n-Google-Drive.

5. In Authorized redirect URIs, click Add URI and enter:

   http://localhost:5678/rest/oauth2-credential/callback

   If you are self-hosting on a different host or port, replace localhost:5678 with your actual n8n instance URL. For n8n running on https://n8n.yourdomain.com, the redirect URI becomes https://n8n.yourdomain.com/rest/oauth2-credential/callback.

6. Click Create.

7. Copy the Client ID and Client Secret immediately. The secret is displayed only once; if you lose it, you must regenerate the credential.

Step 4: Add the Credential in n8n

1. Open your n8n instance in a browser.
2. In the left sidebar, click Credentials > Add Credential.
3. Search for Google Drive OAuth2 API and select it.
4. If using Managed OAuth2 (n8n Cloud): Select the managed option and follow the in-platform OAuth flow. No Client ID or Secret is needed.
5. If using Custom OAuth2:
   • Paste the Client ID from Google Cloud Console.
   • Paste the Client Secret.
   • Leave Authorization URL, Access Token URL, and Token Refresh URL at their defaults.
   • Enter the scope: https://www.googleapis.com/auth/drive
6. Click Sign in with Google. A popup opens to Google’s consent screen.
7. Select the Google account you added as a test user and click Allow.
8. After successful authorization, n8n displays a green confirmation. The credential is now saved and reusable across all workflows.

Step 5: Build Your First Automated Workflow

Trigger Workflow: Watch a Folder for New Files

1. Add a Google Drive Trigger node.
2. Select the credential you just created.
3. Choose the Drive (My Drive or a Shared Drive).
4. Set Watch to Folder and provide the folder ID (found in the Drive URL: https://drive.google.com/drive/folders/{FOLDER_ID}).
5. Set Events to File Created.
6. Add a downstream node such as Gmail to send a notification, or HTTP Request to forward the file metadata.
7. Click Execute Node to test. Drop a file into the monitored folder to verify the trigger fires.

Action Workflow: Download and Process a File

1. Add a Google Drive node with operation Download File.
2. Provide the file ID from a previous node’s output or an input field.
3. Connect a Convert to File or Extract from File node to parse the downloaded content.
4. Route the parsed data to Google Sheets, a database, or Slack for distribution.

Cross-Platform Sync: Google Drive to Airtable

1. Google Drive Trigger watches for File Created in a specific folder.
2. Google Drive node downloads the file.
3. Extract from File node parses CSV/Excel data.
4. Airtable node inserts rows matching the extracted data.

n8n maintains 1,000+ integrations, so Drive can be the trigger or the destination in virtually any business stack.

Troubleshooting Table

Error	Root Cause	Fix
redirect_uri_mismatch	Redirect URI in Google Cloud Console does not exactly match n8n’s callback URL	Verify no trailing slash, no trailing space, same protocol (http vs https), same port
Access denied / App not verified	Missing test user in OAuth consent screen	Add your Google email as a test user in Google Cloud Console > OAuth consent screen > Test users
invalid_client	Client ID or Secret typed incorrectly	Re-copy from Google Cloud Console. Regenerate if lost
insufficient_scope	The scope configured in n8n does not match Google Cloud’s configured scopes	Align scopes in both places. Use https://www.googleapis.com/auth/drive for broad access
403 Forbidden	Drive API not enabled	Return to APIs & Services > Library and confirm the Drive API is “Enabled”
Refresh token expired	OAuth refresh tokens expire after 6 months of inactivity, or if you revoked access via Google Account settings	Re-authenticate by clicking “Sign in with Google” in the credential configuration
Trigger not firing	Polling interval too long, or watching wrong folder	Reduce polling interval in trigger node settings; verify folder ID

FAQ

Do I need a Google Workspace account?

No. A standard free Google account (@gmail.com) works. Google Workspace adds the ability to use shared drives and the Internal user type on the OAuth consent screen, which simplifies testing.

How long does the connection stay active?

OAuth refresh tokens remain valid indefinitely as long as the integration is used at least once every six months. n8n automatically refreshes access tokens in the background. If you revoke access via Google Account settings, you must re-authenticate.

Can I connect multiple Google accounts to one n8n instance?

Yes. Create separate credentials in n8n (one per Google account), each with its own Client ID and Secret from distinct Google Cloud projects, or by reusing the same project and adding the additional account as a test user.

Is the integration GDPR-compliant?

n8n processes data locally if self-hosted. The OAuth2 tokens are stored in n8n’s encrypted database. File contents pass through your n8n instance during workflow execution. For compliance, ensure execution data is encrypted at rest and that your self-hosted instance runs in a GDPR-compliant region.

What changed in n8n v2.0 (2026) for Google Drive?

n8n v2.0 introduced a redesigned editor, improved credential management, Managed OAuth2 support for n8n Cloud users, and enhanced binary data handling that benefits file download/upload workflows. The Google Drive node itself is backward-compatible; existing 1.x workflows import without modification.

Can I automate Google Drive without n8n being online all the time?

Yes. For self-hosted instances, run n8n on a server, Raspberry Pi, or cloud VM that stays online. n8n Cloud instances run 24/7. The Google Drive Trigger polls periodically; if n8n is offline during a file event, that event is missed unless you implement a catch-up mechanism.

What are the rate limits?

Google Drive API enforces a per-user limit of 10,000 queries per 100 seconds per project, and 10,000,000 queries per day. For most workflow automation use cases, these limits are never approached. n8n’s trigger polling defaults to every 60 seconds, which equals 1,440 requests per day far below the quota.

Sources

• n8n Google Drive Node Documentation
• n8n Google Drive Trigger Documentation
• n8n Google OAuth2 Single Service Credentials
• n8n Google Drive Integration Page
• Google Drive API Documentation
• Google OAuth 2.0 for Web Server Applications
• n8n v2.0 Release Notes
• Google Workspace Studio vs n8n: 2026 Automation Guide (Evalics)
• GrowwStacks: How to Connect Google Drive to n8n (2026)