Connect n8n to Google Sheets with OAuth: Step-by-Step Setup

Google Sheets is often the fastest way to make a lightweight workflow useful to a small team: collect form responses, review leads, or maintain a simple approval queue. To connect it safely to n8n, you first need an authorized Google credential.

This guide explains the two common OAuth paths, how to test them, and where to look when access fails.

1. Choose the right authentication path

n8n supports Google OAuth credentials. Depending on where n8n is hosted and which node you're using, your setup experience may differ.

Setup	Best starting point
n8n Cloud, supported Google node	Managed OAuth when available
Self-hosted n8n	Custom OAuth credentials
More specialized Google API integrations	Review the specific node's authentication documentation

Don't assume every Google node offers the same options. n8n's credential documentation says managed OAuth is available for certain Google nodes on n8n Cloud, while custom OAuth requires a Google Cloud app configuration.

2. Managed OAuth on n8n Cloud

If your Google Sheets credential screen offers Sign in with Google, use that path for a straightforward setup:

1. Add a Google Sheets node to a workflow.
2. Select an operation that matches your goal, such as reading rows.
3. Create a new Google Sheets credential.
4. Choose the managed Google sign-in option if offered.
5. Sign in with the account that can access your target spreadsheet.
6. Review and approve the requested permissions.

Then select the intended document and worksheet, execute the node with a non-sensitive test sheet, and confirm that the returned rows match what you expected.

3. Custom OAuth for self-hosted n8n

When managed sign-in is unavailable, create your own Google OAuth application:

1. In your Google Cloud project, configure the necessary OAuth consent settings.
2. Enable the Google APIs required by your workflow, including the Sheets API where applicable.
3. Create an OAuth client appropriate for your n8n installation.
4. Copy the OAuth Redirect URL displayed by n8n into the Google Cloud OAuth client's authorized redirect URIs.
5. Enter the client ID and client secret into n8n's Google credential form.
6. Complete the Google authorization flow and save the credential.

Use the redirect URI shown in your own n8n credential screen rather than copying someone else's example. The public hostname, TLS configuration and reverse proxy must all agree with that URI.

A self-hosted n8n installation reachable only on localhost cannot serve as a publicly usable endpoint for every OAuth flow. Configure your public URL correctly before troubleshooting more obscure credential settings.

4. Test spreadsheet access carefully

Start with a test spreadsheet containing simple sample data:

Name	Status
Taylor	New
Sam	Contacted

In the Google Sheets node, choose an operation to read rows. Select the spreadsheet and tab, then execute the node manually. Validate that the correct account has access, the sheet is named correctly, and any downstream mapping uses the actual field names.

For workflows that write rows, test on a separate sheet first. A mistaken append or update action can create duplicate records or overwrite real customer information.

5. Fix common OAuth problems

redirect_uri_mismatch

The redirect URI configured in Google Cloud does not exactly match the URI used by the authorization request. Compare protocol (https), hostname, path and trailing slash carefully. Use n8n's displayed redirect URI as the source of truth.

Google says the app is not available to this account

Check the OAuth consent configuration and whether your app is in testing mode with an authorized list of test users. For organizational accounts, an administrator's restrictions may also apply.

The credential connects, but the node receives 403

The signed-in account may lack access to the spreadsheet, the relevant API may not be enabled, or the credential may lack the needed scopes. Confirm the exact Google account, spreadsheet sharing permissions and selected node operation.

The connection worked yesterday but fails now

Review the credential's authorization status, possible revoked permissions, account policy changes and any refresh-token errors. Avoid assuming every 401 or 403 has the same cause.

6. Protect customer data

Use the least-privileged account and scopes your use case supports. Do not post OAuth client secrets, access tokens or spreadsheet contents in a public troubleshooting question. Share only redacted logs and anonymized screenshots.

For production workflows, decide who owns the credential and what happens when that person leaves the business. Document the reauthorization procedure, and test error handling before connecting the workflow to live leads or invoices.

Useful references

• n8n: Google credentials
• Google Cloud: OAuth 2.0

The takeaway

Managed Google sign-in is the simplest route when offered. For self-hosting, custom OAuth requires correct consent, APIs, client credentials and an exact redirect URI. Once connected, test read access first and only then enable write operations.