Issue Configuring OAuth2 with Gmail on n8n Cloud

Questions
1

Hello everyone,

I’m encountering difficulties while setting up OAuth2 authentication with Gmail on my n8n Cloud instance.

Here’s the issue:

When I try to create an OAuth2 connection for Gmail, the option to input my Client ID and Client Secret does not appear.
Instead, I’m forced to select the “Sign in with Google” option, which prevents me from setting up my custom OAuth2 credentials. When I click on OAuth2 (recommended), I don’t see the fields for OAuth Redirect URL, Client ID, or Client Secret.

I have already generated a Client ID and Client Secret in Google Cloud Console and configured the redirect URI as follows:
https://[my-instance].n8n.cloud/rest/oauth2-credential/callback.

I want to use my custom credentials to personalize the connection because the automatic Gmail connection is not sufficient. However, I can’t input my credentials because the fields don’t show up.

Questions:

  1. How can I enable the option to manually input a Client ID and Client Secret in the OAuth2 configuration?
  2. What steps should I take to make this work?

Thank you so much for your help in advance!

1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

I am also having a similar problem. When I click OAuth2 (recommened) none of the fields below it appears. Instead, I am forced to choose “Sign in with Google,” which does not work.
I am using the free trial on the cloud.
Please help, so that I can select the OAuth (Recommnded) option.

1 Like
4

Hey @VICOS,

Welcome to the community :raised_hands:

On n8n cloud we manage and have had the app verfied by Google which means you get the one click sign in option. There is no way to disable this, Is there a reason why you don’t want to use the one we provide?

1 Like
5

@skb when you say it doesn’t work what do you mean? do you get an error?

7

No, as per earlier comment by Jon n8n cloud app is already verified by Google. All you need is to sign on. You are offered OAuth Redirect URL, Client ID, and Client Secret when you self-host your n8n instance. Google does not know about that instance yet and thus you need to have it verified.

8

Hi @Jon ,
I had selected as credential “Sign in with Google”, and yes, it was giving an error and not sending the mail.

However, I was able to fix the problem by enabling popups in the browser. It seems for both Outlook and Gmail, if using credentials as “sign on,” popups need to be activated.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.