I’m getting 404 - The resource you are requesting could not be found / Requested entity was not foundfrom the Google Sheets node whenever I try to select a sheet tab or run “Append Row.” It happens on every spreadsheet, including brand-new blank ones I create fresh.
Setup:
n8n Cloud, version 2.30.8
Google Sheets node, Append Row operation
Google Sheets API and Google Drive API both enabled in a Google Cloud project
What I’ve already ruled out:
The spreadsheet exists and is owned by the same Google account I authorized n8n with (verified matching accounts)
Sharing set to “Anyone with the link” (Editor)
Document by URL with the full, clean URL — 404
Document by ID with only the correct long ID (the string between /d/ and /edit, not the gid) — still 404
Sheet by Name typing the exact tab name instead of using the dropdown — still 404
Deleted and recreated the credential; re-authorized after enabling the APIs
Tested on a fresh blank sheet — same 404
Note: I found the solved thread where the fix was “use the long ID, not the gid” — I confirmed I’m using the correct long spreadsheet ID and it still 404s, so my case seems different.
Gmail nodes on the same Google account work fine, so the account/auth itself seems okay — it’s specifically the Sheets node that can’t find any resource.
The Sheets credential only offers “Sign in with Google” (managed OAuth) with no fields to enter my own Client ID/Secret — is that relevant? Is there a way to supply custom OAuth credentials on Cloud, or is this a known issue with the managed Google integration?
Since Gmail works but Sheets doesn’t on the same account, this points to the OAuth token itself missing Sheets/Drive scopes rather than sharing or ID issues.
With n8n Cloud’s managed “Sign in with Google,” when you go through the consent screen Google shows a list of checkboxes for each requested scope (Gmail, Sheets, Drive, etc.), and depending on the flow some of them can end up unchecked by default — the token you get back is then valid but simply doesn’t carry the Sheets/Drive grant. Enabling the APIs in Google Cloud Console isn’t the same as the token having consented to use them.
Worth checking:
Go to your Google Account → Security → “Third-party apps with account access”, find the n8n connection, and check exactly which scopes it lists. If Sheets/Drive aren’t there, that’s the 404 explained.
Delete the credential in n8n, create a new Google Sheets credential, and when the Google consent screen appears, make sure every checkbox (Sheets and Drive) is explicitly ticked before continuing — don’t rely on “select all” links that sometimes miss one.
If it’s still missing after re-consenting, revoke n8n’s access entirely from the Google Account security page first, then reconnect from scratch (a stale token can otherwise be reused instead of a fresh consent).
That would also explain why Gmail is fine — it’s a separate scope that did get granted.
Hi @steveetee
Yes, you can supply your own Google OAuth on Cloud. The “Sign in with Google” you’re seeing is n8n’s managed OAuth (Cloud only), and that shared app is the part failing here. In the credential, use the authentication dropdown to switch from Managed OAuth2 to Custom OAuth2, which reveals the Client ID and Client Secret fields. Create an OAuth client in Google Cloud Console (Sheets and Drive APIs enabled), copy the OAuth Redirect URL shown in the n8n credential into its Authorized redirect URIs, then paste your Client ID and Secret back into n8n and sign in. The node then runs through your own Google app instead of the shared managed one.
See this:
Test the credential against one new sheet shared directly with that account. If that works, compare spreadsheet ownership and drive location before rebuilding the workflow or changing node settings.