OAuth Login / Google Sheets Trigger – Error: “Something went wrong. Please try again!”

Questions
1

<Hi everyone,
I’m trying to create a credential for the Google Sheets Trigger in n8n.cloud, but I keep getting this error after signing in with my Google account:
“Something went wrong. Please try again!”
(This happens even in Incognito mode, with VPN turned off and browser cache cleared.)
Details:
I’m using n8n.cloud (not self-hosted)
I’ve tested multiple Google accounts
The credential doesn’t get created – error occurs before the access token is issued
The issue seems to be related to the redirect URI:
https://oauth.n8n.cloud/callback
Question:
Could you please check if this redirect URI is correctly listed in your OAuth app’s authorized redirect URIs?
Thanks in advance for your help!!-- Hey! The fastest way to find solutions is by using the :magnifying_glass_tilted_right: search function at the upper right.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Does it happen to other google nodes such as google drive, gmail node other than googlesheets node?

Also, I presume you have added the redirect url in your google cloud console?

3

I can help you with this you’re likely hitting a behavior change in how Code nodes resolve data from other nodes, not something you broke.

When a Code node hangs while accessing $("OtherNode").item, it usually means one of two things:

  • The referenced node is no longer in the same execution branch

  • The Code node is trying to access data before it exists, which in newer versions can deadlock instead of throwing an error

This used to fail loudly; now it can just spin.

To pinpoint it, I’d look at:

  • Where the Code node sits relative to the Merge node

  • Whether the Merge outputs zero or multiple items

  • Whether the Code node runs per item or once per execution

In most cases, the fix is either:

  • Passing the required data explicitly into the Code node, or

  • Replacing $("Merge").item with a safer pattern like input data or $items()

If you’re open to it, share the workflow (or just the Merge → Code section), and I’ll help you refactor it so it runs reliably again.

[email protected]