Problem with Credentials

Questions
1

I can’t sign in with google in my Youtube OAuth2 API. When I try to sign in, a warning appears:

“Only users within the organization can access the n8n-local app. If you believe you should have access, please contact the developer”. I assumed this happened because I tried to log in using an email address different from the one I used to create the workflow; however, when I tried logging in with the original email, the same warning appeared, preventing me from proceeding with the automation. I don’t know if this is happening due to an amateur mistake or if it’s a bug. I’m a complete novice when it comes to automation and IT; I was building this workflow to supplement my income. Would anyone know how to solve this problem?

2

Hey @Gabriel_Nascimento_C, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@jcuypers, @Glorious, @AnthonyAtXRay - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Hi @Gabriel_Nascimento_C

Your Google Cloud Project is configured with an “Internal” User Type, which restricts access exclusively to users within your Google Workspace organization.

This is a common configuration error in the Google Cloud Console (GCP) and is not a bug in n8n or an issue with your email address.

Since you are likely using a personal Gmail account or trying to access the app from outside a corporate domain, you must change the app’s visibility.

  1. Open Google Cloud Console: Go to the Google Cloud Console.
  2. Select your Project: Ensure the project you used to create the YouTube API credentials is selected in the top dropdown menu.
  3. Navigate to Consent Screen: In the left-hand sidebar, go to APIs & Services → OAuth consent screen​.
  4. Change User Type:
    • Look for the User Type section.
    • Click Change App or Edit App​.
    • Select External instead of “Internal”.
    • Click Save and Continue​.
  5. Add Test Users (Crucial Step):
    • Because your app is now “External” but not yet “Verified” by Google, it is in Testing mode​.
    • Scroll down to the Test users section.
    • Click + ADD USERS​.
    • Enter the exact email address you are using to sign in to YouTube.
    • Click Save​.

Now, go back to n8n and attempt to connect your YouTube OAuth2 credential again. It should now allow you to proceed (you may see a warning that “Google hasn’t verified this app”—simply click Advanced → Go to n8n (unsafe) to continue).

Does that help?

4

Hi @Gabriel_Nascimento_C Welcome!
The Internal audience only exists on Cloud projects that sit inside a Google Workspace or Cloud Identity organization, and Google rejects every account outside that organization, which is why your own Gmail fails as well. If the project was created under a work or school account, that organization’s admin controls the audience and you can get stuck there.
Rebuild it on a plain personal Google account instead: create a new project in the Google Cloud Console signed in with that account, enable YouTube Data API v3, configure the consent screen (a project with no parent organization can only be External), create an OAuth client of type Web application with the redirect URL copied from your n8n credential, then paste the new Client ID and Secret into the YouTube credential.
While the app stays in Testing, consent and the token expire after seven days, so reconnect the credential in n8n when the node stops working.

5

Thank you so much! You saved my project :folded_hands:

6

Thank you! Your instructions helped me a lot.