Editorial status: Documentation-based implementation guide. No independent end-to-end workflow test or downloadable workflow JSON is claimed.
Connecting Google Sheets to n8n usually starts with a credential, but the correct OAuth setup depends on whether you use n8n Cloud or a self-hosted instance. This guide explains the decision points and a practical troubleshooting sequence without asking you to expose access tokens.
Choose the correct authentication route
On supported n8n Cloud configurations, the Google credential interface may provide a managed sign-in flow. Self-hosted instances often require you to configure your own Google Cloud OAuth client and redirect URI. Follow the instructions shown in the credential dialog for your installation rather than copying a callback URL from someone else’s tutorial.
Prepare Google access
- Identify the Google account that should own or edit the spreadsheet.
- Create a test spreadsheet with a simple header row.
- In n8n, create a Google Sheets credential and inspect the available connection method.
- If using a custom OAuth client, configure the relevant Google APIs, consent-screen settings, and authorized redirect URI as directed by n8n.
- Complete the sign-in flow and confirm the credential connects successfully.
Build a minimal verification workflow
Use a Manual Trigger followed by a Google Sheets node configured to read a known test range or append a harmless test row. A tiny workflow isolates credential problems from complicated field mapping. Keep the test sheet separate from production reporting.
Fix redirect URI mismatch
If Google reports a redirect URI mismatch, compare the URI displayed by n8n with the one configured on the Google Cloud OAuth client. The scheme, domain, path, and trailing characters must match the provider’s requirements. Self-hosted sites behind a reverse proxy should verify that n8n generates the intended public HTTPS URL.
Fix permission denied or missing spreadsheet
Check that the signed-in Google account can open the spreadsheet directly. Verify that you selected the correct document and tab, and that the account has editor access for write operations. If you use a service account instead of OAuth, the spreadsheet may need to be shared with that service account’s identity; support and restrictions vary by setup.
Fix expired or revoked access
Credentials can stop working after a Google account security change, a revoked grant, or a misconfigured OAuth consent screen. Reconnect the credential through n8n’s credential manager, then rerun the minimal verification workflow. Do not paste client secrets or refresh tokens into a public support thread.
Verify your field mapping
A successful OAuth connection does not guarantee a successful append. Confirm the destination header names and use the n8n input pane to map fields from the previous node. If your spreadsheet schema changes, revisit the node configuration and rerun a test.
Production checklist
Use least-privilege access, keep credentials owned by a managed business account when appropriate, restrict who can edit the workflow, and establish a procedure for reconnecting access when an employee leaves.
Official references
Documentation reviewed: October 2026. Always verify node options in your installed n8n version before using a workflow with production data.