Ive authorized myself by clicking “Sign in with Google”, and I see I see “Account connected”.
However, there is no oauth2 callback URL showing preventing me from using the Google APIs.
I get the oauth2 callback url showing after authenticating with Google on my self-hosted n8n, and I expected the same behaviour on the cloud version.
How do I get the oauth2 callback url so I can use the Google APIs?
It looks like your topic is missing some important information. Could you provide the following if applicable.
On n8n cloud the OAuth setup is pre-configured, and the callback url is fixed for that configuration. That way users do not need to configure these credentials from scratch.
Since the screenshot says “Account connected”, are you seeing any issues with any particular node when trying to execute that node? From what I can tell, you should be able to use Google APIs already.
Thanks for answering quickly 
The Google Sheets node is unable to load my sheets
2nd Question:
Where can I find the callback URL that you mention is fixed for the configuration? I would need this webhook if I ever want to configure a google cloud console project and attach any desired API.
Hey @Joejoe,
Can you make sure you are on at least 1.75.0? When you try and use a credential that needs a client id or secret the UI will show you the callback URL, The Google Drive node is a good example of one that would need the manual configuration for now.
We are hosting our n8n on n8n.cloud, how do I upgrade to the latest version?
I see the OAuth2 callback url, client id and password in the Google Drive node. Now I need to be able to get the Google Sheet node working, and appreciate your support to get this matter resolved.
Hi,
I have the same issue than @Joejoe
I used to have credentials with Google Sheets OAuth2 API that work perfectly. But since last upgrade in N8N version (I am on version 1.74.3
now) I have issues with google sheets credentials / node to find my files. I don’t know if it is linked to the version upgrade or not.
I am using my Google Workspace domain address. It used to work perfectly before the version upgrade. 
Is there any changes in the way to create credentials in N8N?
It is good to hear that it is just not me having this trouble, unfortunetly. This case is still open for me. I still need assistance from the n8n team and I am awaiting their response.
I wish I could have given you an answer, @sssamsss8
We are experiencing an issue with the integration of Google Drive credentials, which is preventing us from using tools such as Google Sheets.
A few days ago, we encountered failed iterations with PostgreSQL, but that was resolved with the new update that was released. However, as of today, the Google Drive credentials seem to be failing. We have tried creating new credentials to address the issue, but the error persists, and it seems as if the credentials cannot be properly verified.
Could you please assist us in identifying and resolving this issue?
Thank you for your support.
If you are having issues with credentials not working upgrade to 1.75 which will fix the oauth issues.
If you are expecting to see client id and client secret it isn’t something that is available on some Google applications when using cloud as we have a managed app that has been verified by Google.
Check the note at the top of this page to see the nodes that only have the sign in with Google button: Google OAuth2 single service | n8n Docs oddly Google drive needs to be removed from that list so I will get it updated.
