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:
Click on the circle button in the OAuth section to connect a Google account to n8n.
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)ā.
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ā¦
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.
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.
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?