Error 403 using OAuth Credential from Google

Hi, there!
I just started experimenting with hosting my own cloud server and, after deploying it, I tried to create my first workflow, but got stuck at step 11. from Using OAuth, that is:

  1. Click on the circle button in the OAuth section to connect a Google account to n8n.

When I click Sign in with Google:
image

I get the following error

Do I have to take any action to have my credentials verified by Google?

1 Like

Yes, Google is getting quite complicated with some scopes. Normally it is however not a problem if you are in the same organization as the app you are authenticating with. In this case, do you create the App via the same account you want to now authenticate with?
But even if that is not the case I get normally a window saying ā€œGoogle hasn’t verified this appā€ but then I can click on ā€œAdvancedā€ and then on ā€œGo to (unsafe)ā€.

2 Likes

Yes. I am using the same account.

Actually, everything is pretty much new for me. I mostly went with the steps listed in the Docs and, during the process, Google required a lot more things like: Consent screen, Scopes, Domain Verification… :sweat:

Finally I got it to work after registering that same account as a test user for the App.
Then went to a similar process of:

Now my workflow is running (return some YouTube videos). But I don’t know if it is necessary to push the App to production, only to be able to keep this workflow running.

image

I’m getting the same exact error as you and I’m confused about what you did to eventually solve this.

I’m trying to auth as the same Google account.

Hi, @Steven_Irby!

I created a credential:

Then edited it adding my domain and the callback url. Though, I am not sure if the first is really needed.

After that, at the ā€˜OAuth consent screen’ page, I added my own account e-mail as a test user:

That fixed the error.

5 Likes

Thank you so much for the quick reply! I got it working now. :slight_smile:

1 Like

Hey @thiagonascimentodf and @Steven_Irby!

You can even publish the app if you want to don’t want to use it as a test user. I’ve added the steps in the documentation that shows the steps to Configure Consent Screen. Once it is merged, I’ll share it here.

2 Likes

Hey there! I’d love to reopen this subject if you don’t mind. I did all that on my side and it worked fine. However, every 7 days the authorization token gets expired. So I thought about to go through the pain of verification my ā€˜app’ by Google (although there’re no direct external users of this flow). But I haven’t managed to figure out the right scopes (my flow uses several ā€˜sensitive’ scopes according to google related to gdrive, gsheets). Did you face that authorization token expiration while being in testing mode? If so, how did you manage keeping authorization token valid or recreated?

i did everything you said but is not working since some days

thank you it’s great

nice instruction, save my time!