How to Use Google Sheets With n8n

Updated 2026-10-07 · 1196 words

This page may contain affiliate links. If you buy through them we may earn a commission at no extra cost to you.

Direct answer: using Google Sheets in n8n means adding a Google Sheets node, authenticating it with a Google OAuth2 credential set up in Google Cloud Console, and picking an operation, Read, Append, Update, or Delete, against a specific spreadsheet and sheet tab. The OAuth setup in Google's console is the only genuinely fiddly part; once that credential exists, reading and writing rows in a workflow takes a couple of minutes per node. Here's the full setup, including the trigger pattern Sheets doesn't offer natively.

Step 1: Set up the Google Cloud OAuth credential

Before n8n can touch your spreadsheet, you need a Google Cloud project with the Google Sheets API enabled and an OAuth2 client ID and secret. In Google Cloud Console, create a project (or use an existing one), enable the Google Sheets API under APIs & Services, then create an OAuth client ID under Credentials, choosing "Web application" and adding n8n's OAuth redirect URL (n8n shows you this exact URL when you create the credential). Set the OAuth consent screen to Production rather than leaving it in Testing; a Testing-mode consent screen expires its tokens after about a week and forces you to re-authenticate repeatedly, which is the single most common frustration people report with this setup and has nothing to do with n8n itself.

Step 2: Add the credential and connect a spreadsheet

Back in n8n, create a new Google Sheets OAuth2 API credential with the client ID and secret from Step 1, and complete the OAuth flow by signing into the Google account that owns (or has edit access to) the target spreadsheet. Add a Google Sheets node, select the credential, and pick your spreadsheet either from the dropdown (if you're signed into the right account) or by pasting its URL directly.

Step 3: Read rows

Set the operation to Get Row(s) and specify the sheet tab (not just the spreadsheet, a single Google Sheets file can hold multiple tabs, each addressed separately). You can pull the whole sheet or filter by a range. The node returns each row as a JSON object keyed by your header row's column names, which makes referencing a specific field downstream, {{ $json.Email }}, for instance, straightforward without manual column-letter mapping.

Step 4: Append new rows

Switch the operation to Append to add a new row to the bottom of the sheet, mapping each column to a value from an earlier node. This is purely additive: appending data that matches an existing row's content won't update it or flag a duplicate, it just adds another row. If your workflow is logging events (form submissions, completed tasks), that's exactly the behavior you want; if it's meant to keep a record current, append is the wrong operation.

Step 5: Update existing rows without duplicating data

For anything that should modify an existing row rather than add a new one, a customer's status changing, a running total updating, use the Update operation and set a matching column, commonly an email address, order ID, or another unique identifier already in the sheet. n8n finds the row where that column matches your input and updates only the fields you specify, leaving the rest of the row untouched. Skipping this distinction, using Append when you meant Update, is the most common Google Sheets mistake we've seen in workflows that are meant to track live state instead of an append-only log.

Step 6: Build a trigger, since Sheets doesn't push one natively

Unlike apps that offer a native "new record" webhook, Google Sheets has no built-in way to notify n8n the instant a row changes. The reliable workaround is a Schedule Trigger running on an interval that fits your use case (every five minutes is common), followed by a Google Sheets node reading recent rows, then a comparison step, checking a timestamp column, or tracking the last row number you processed in n8n's static data or a separate tracking sheet, so you only act on rows you haven't already handled. This pattern is slower than a true push-based webhook, acceptable for most internal tracking use cases, and worth knowing about before you spend time hunting for a native trigger that doesn't exist.

Step 7: Watch the API's rate limits on bulk operations

Google's Sheets API enforces per-minute read and write quotas per project. A workflow that loops through hundreds of rows writing one at a time can hit this limit mid-run, surfacing as a sudden batch of failures partway through. For bulk writes, batch multiple rows into a single Append or Update call where the node supports it, or add a short delay (a Wait node) between batched requests rather than firing them as fast as the loop allows.

Where this fits with other tools

Google Sheets is often the simplest destination for a workflow's output before a team is ready to stand up a real database, several of the automation guides on this site use it exactly that way, including our data entry automation guide and our invoicing automation guide, both of which write extracted or calculated values to a tracking sheet as the final step. If your spreadsheet needs are outgrowing plain rows and columns, linked records, views, native automations, our best Airtable automation tools roundup covers the next step up, and it's worth reading before you build more logic on top of a sheet that's starting to strain under the weight of what you're asking it to do. If you're ready to move past Sheets entirely, our guide to connecting n8n to a database covers the Postgres and MySQL setup, including the SSL and reachability details that trip up a first connection.

Google Sheets vs. a proper database in n8n

Common pitfalls

The OAuth consent screen left in Testing mode causes more repeated-authentication complaints than any other part of this setup; publishing it to Production fixes this permanently and takes under a minute. The second is confusing Append and Update, leading to duplicate rows in a sheet that was meant to track current state rather than log every event. Third, remember a spreadsheet can have multiple tabs; selecting the wrong one is a quiet failure, the node runs without error, it's just reading or writing to an empty or unrelated tab.

For the API-level reference behind the node, Google's Sheets API documentation covers quota specifics and advanced range syntax beyond what this guide needs. Get the OAuth credential set to Production, pick Append or Update deliberately rather than by habit, and build the polling trigger pattern once rather than per workflow; those three decisions account for nearly every Google Sheets issue we've run into in n8n.

Save this to Pinterest