What are you trying to achieve?
I’m building an automation where MAKE connects to YouTube using a Google Cloud OAuth app set to internal access, within a Google Workspace domain. The objective is to obtain non-expiring (long-lived) tokens by ensuring that both the app and user are internal to the organization, as required by Google.
Steps taken so far
Created a Google Cloud project and configured the OAuth consent screen as internal, restricted to users within my verified Workspace domain.
Verified the domain (buzzmakers-agency.com) in Google Workspace; domain is active and Gmail-enabled.
The user authenticating in MAKE is internal to the domain (javi@…), and is the primary owner of the Google Cloud project and of the YouTube channels.
The same user also appears as the primary owner of the OAuth app.
The internal app successfully connects to the YouTube account and lists all channels associated with it.
However, the YouTube channels were originally created under a different account and later transferred to this Workspace user.
While the channel selection screen in MAKE correctly displays all channels, the connection only works for the originally owned channel, not for the transferred ones.
When selecting any of the transferred channels, the following error appears:
Error 403: org_internal — This app can only be used within your organization.
1 Like
I’m having the same issue, and can see others have had so in the past - but can’t seem to find an answer on it.
1 Like
Even if you ask youtube support, with the particular question, they just send the general link with the general information. Seems to be difficult to find a solution. 
1 Like
I should say too - it’s not just for transferred accounts - but second channels in the account. @Michaela - is there support in the community around this? I’ve noticed this question has been asked a few times with no response from anyone on the make team - some helpful hints would be appreciated!
1 Like
Javier, I’ve tried a million different things, since I last posted. The main things that worked (I think, because I also think the Youtube Module I was using is broken)..
- Changing the Audience (Google Cloud Project / Google Auth Platform/Audience) to External & Testing, then added my email address (the account owner) in the Test Users. When I authenticated in in Make.com - it gave me a warning to tell me the app wasn’t verified, but I could continue past that anyway.
- Adding a MILLION URI’s - see this post - Google Docs Error 400: redirect_uri_mismatch - #7 by samliew
- And then I also changed the Module I was suing - instead of using the create a playlist, I tried upload a video and then I was able to authenticate. I just went back to the old module, and used the connection I had created in the other module, and it worked (As in, I logged in as me, and then it listed the different channels under my account). So it just might be the module.
It was painful - good luck!
1 Like
Try adding the account logging in to the list of test users.
For more information, see
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Hi Jessica and Sam,
I just wanted to sincerely thank you both. Thanks to your advice, I was finally able to solve the issue and get permanent tokens working properly. 
What worked for me was:
Setting the OAuth audience to External and adding the authenticated user as a Test User .
Regenerating the YouTube connections from scratch inside Make after setting the app in Test mode.
After following these steps, the OAuth flow completed successfully, and now the tokens are staying valid without needing to refresh them daily.
It was a long road, but your guidance really made a difference! I truly appreciate your help and the time you took to share your experience.
Thanks again and best wishes to everyone dealing with this tricky setup! 
1 Like
Good result! You’re welcome