Hi, I’m new to n8n. I’ve installed it in a local VM, currently without a Domain attached. I’m fully aware such a setup already brings a lot of limitations. But before I go through a real, self-hosted install WITH a domain on a VPS, I wanted to know:
Does the Community Edition in a self-hosted scenario (with a real domain name on a public IP, valid certificates etc.) support the “Google Sign-In” button?
I saw that I can provide a callback url for Google OAuth2 in the community version, but that would also require having a Google Cloud account, which is too much overhead (from the Google side) for a bit of playing with the app and Google Docs.
So, just the simple question: Does the CE have the Google Sign-In button and support for OAuth with only a Gmail address, without Google Cloud account or Google API key?
You will need to setup an app in your google account and connect that with n8n for oauth2 to work. That is simply how it works. On cloud n8n has done this for you with their own app in google.
And then you can use your own account or a service account like @Sebas suggested to connect.
I do wonder how you expect to use google services without having an account though. Might have misunderstood though.
We started using n8n hosted pro plan and there every single user can just click “Sign In” and use their own Google drives/sheets etc…
Now that we’ve switched to self-hosted enterprise version, nobody can do it… Is there a way for devops/admins to set this up once and all other member’s can just sign-in as in pro plan?
PS: I did it as described in documentation but that only solves it for me. Still everbody else has to do go through the hassle of creating GCP projects, oauth consent screens etc… there has to be a way to provide this otherwise n8n is mixing up their plans. Pro shouldn’t be better than enterprise.
I dont have the responds, but, in that case i will try with the admin account of the google workspace and check the options in the api and credential section to see if some option are available to share the api access to all members of the workgroup. I’ll check this because it’s a really good approche for company !
Already tried, if you share the same credential, everytime somebody re-authenticates with their google account it will change it for everybody else too. So far the only way I can find for people to independently use their own credentials is for each one of them to go through the hassle of creating a google cloud project, setup oauth consent screen, create a credential and copy/paste needed data back to n8n.
Solved with CREDENTIALS_OVERWRITE_DATA env variable.
Careful docker compose or n8n doesn’t like escaped double quotes or wrapping single quotes, just put your json as is without and " " (space) in it.