How to Connect Google Drive to n8n (Complete Setup Guide)

Connecting Google Drive to n8n opens up a massive range of automation possibilities — from automatically saving files to a shared folder, to reading spreadsheets, uploading reports, and triggering workflows when new files appear. In this guide, we walk through the full setup process step by step so you can get Google Drive working inside your n8n workflows quickly and reliably.

Whether you’re building a document management system, an automated reporting pipeline, or a file-processing workflow, Google Drive is one of the most useful integrations n8n offers.

Why Connect Google Drive to n8n?

Google Drive is where many teams store their most important files — spreadsheets, PDFs, images, and documents. When you connect it to n8n, you can automate tasks that would otherwise require manual intervention every time. Instead of downloading a file, processing it, and re-uploading it by hand, your workflow can do all of that automatically in the background.

Some common reasons to integrate Google Drive with n8n include: automatically uploading files generated by other nodes (like reports or processed data), downloading files for further processing or analysis, organizing files into folders based on rules, and triggering workflows when new files land in a specific folder. These are just a few of the dozens of use cases the integration supports.

Prerequisites: Google Cloud Console Setup

Before you can connect Google Drive to n8n, you need to set up OAuth 2.0 credentials in the Google Cloud Console. This is a one-time process that authorizes n8n to access your Google Drive on your behalf.

Start by going to console.cloud.google.com and creating a new project (or selecting an existing one). Navigate to APIs & Services → Library and search for Google Drive API. Click on it and hit Enable. You’ll also want to enable the Google Sheets API if you plan to work with spreadsheets from Drive.

Next, go to APIs & Services → OAuth consent screen. Choose External (or Internal if you’re in a Google Workspace org), fill in the required app name and email fields, and save. Then go to Credentials → Create Credentials → OAuth 2.0 Client ID. Select Web application as the application type. Add the redirect URI that n8n provides — you’ll find this in the n8n credentials setup screen. Save and copy your Client ID and Client Secret.

Setting Up Google Drive Credentials in n8n

Inside n8n, open your workflow and add a Google Drive node. Click on the credential field and select Create New Credential. You’ll see two options: OAuth2 (recommended for personal or team accounts) and Service Account (better for server-to-server automation without user interaction).

For OAuth2, paste in your Client ID and Client Secret from the Google Cloud Console. Click Connect my account — this will open a Google authorization popup where you sign in and grant n8n access to your Drive. Once authorized, n8n stores the token and you’re ready to use it in any Google Drive node. For Service Account credentials, you’ll upload a JSON key file downloaded from Google Cloud Console instead.

The Google Drive Node: Available Operations

Once credentials are connected, the Google Drive node in n8n supports a wide range of operations. Under the File resource, you can: Copy a file to another location, Create a new file, Delete a file, Download a file’s contents, Get file metadata, List files in a folder, Move a file, Share a file, and Update file metadata or content. Under the Folder resource, you can Create, Delete, Get, List, and Share folders. This makes the node versatile enough to handle nearly any file management scenario.

Uploading Files to Google Drive

One of the most common uses of the Google Drive node is uploading files. To upload a file, set the resource to File and the operation to Create. You’ll need to specify the File Name, the Parent Folder ID (the Drive folder where the file should land), and the Binary Property that holds the file data.

The binary property is typically populated by a preceding node — for example, an HTTP Request node that downloads a file, a Read/Write Files from Disk node, or a Convert to File node that turns data into a downloadable format. The Google Drive node reads that binary data and uploads it directly. You can also set the MIME type explicitly if needed, or let n8n detect it automatically from the file content.

Downloading Files from Google Drive

To download a file, set the operation to Download and provide the File ID. The File ID is the long alphanumeric string in the Google Drive URL for any file — for example, in drive.google.com/file/d/1ABC.../view, the ID is 1ABC.... You can also retrieve File IDs dynamically by using a List operation first to find the file by name, then pass the ID to the Download operation.

The downloaded file lands in the node’s binary output, where it can be passed to other nodes for processing — such as extracting text from a PDF, parsing a CSV, or sending the file as an email attachment using the Gmail node.

Listing Files and Finding Folders

The List operation is especially useful when you need to find files dynamically. Set the resource to File or Folder, choose List, and optionally specify a Folder ID to narrow results to a specific directory. You can also filter using Google Drive’s query syntax in the Query field — for example, name contains 'report' or mimeType='application/pdf' will return only matching files.

The node returns an array of file objects, each containing the file’s ID, name, MIME type, size, and modification date. You can loop through these with a Split In Batches node or a loop workflow to process each file individually.

Creating Folders and Organizing Files

You can create folders in Google Drive using the Folder → Create operation. Specify a Name for the new folder and optionally a Parent Folder ID to nest it inside an existing directory. The node returns the new folder’s ID, which you can immediately use in a subsequent node to upload files directly into it.

This is perfect for workflows where you need to dynamically create client-specific folders, date-based archive directories, or project-organized storage. Combine it with an IF node to only create the folder if it doesn’t already exist, using the List operation to check first.

Practical Automation Examples

Here are several real-world workflows that use Google Drive integration in n8n. In a daily report archiver, a Schedule trigger fires each morning, a workflow generates a report (from a database or API), converts it to PDF, and uploads it to a dated folder in Google Drive automatically. In a file processor pipeline, files dropped in a Watch Folder trigger the workflow — n8n downloads the file, processes it (OCR, data extraction, format conversion), and saves the result back to a different Drive folder.

For a client deliverable system, when a project completes in a project management tool, n8n automatically creates a client-named folder in Drive, moves the relevant files in, and shares the folder with the client’s email. For a spreadsheet sync, n8n reads a Google Sheet from Drive on a schedule and syncs its data to a database, CRM, or another tool — keeping everything in sync without manual exports.

Tips and Troubleshooting

A few things to keep in mind when working with Google Drive in n8n. First, if you hit permission errors, double-check that the Google Drive API is enabled in your Cloud Console project and that the OAuth consent screen scopes include Drive access. Second, Drive File IDs are permanent — even if a file is renamed or moved, its ID stays the same, making it safe to store IDs in your workflow logic. Third, when listing files, use pagination if you expect more than 100 results — the List operation supports a Return All toggle that automatically handles pagination for you. Finally, for high-volume uploads, consider using Service Account credentials to avoid OAuth token expiry issues.