I’m having a challenge connecting the YouTube OAuth2 API to n8n. The documentation doesn’t make it clearer, and I’ve never struggled so much to get something connected. There’s a video on YouTube that explains how to do it, however the flow seems to have changed, and now it seems like you need a domain and a privacy policy? Am I understanding this right? Seems like an insane amount of hoops to jump through.
1 Like
Yeah YouTube certainly isn’t one of the easier APIs to hook up. It essentially is two steps:
- Setting up your “OAuth” consent screen.
- Creating the OAuth credentials for YouTube.
From what you’re saying, I think the domain and privacy policy are a part of step #1. Privacy policy should be optional, and then the domain should just be for the redirect URL which you can use localhost for if you are just running things locally!