Dec '25 • Question ❓
n8n support if anybody can help
I have a client that needs to connect multiple Gmail accounts to the same n8n instance without sharing the n8n interface with their employees.
My issue is that if you do not use n8n’s built-in signup via nodes, you do not actually save the
credentials inside n8n in a secure way.
You can, of course, create a URL with the secret key, ID, and callback URL, then store the access token
in an HTTP request to perform actions. However, this means you will need to keep the secret key and ID in that HTTP node forever since you must refresh the token every hour.
My question is: has anybody run into this and solved it in a clever way? They want a webpage where their employees can go and sign in, but that is not really how n8n works. As far as I know, n8n is meant more for internal use rather than being used as a SaaS.
2
3 comments
n8n support if anybody can help
powered by
skool.com/ai-first-client-formula-8589
From zero to first $1k/month with AI automation in 30 days. Get the exact formula + templates that landed 100+ their first client.
Suggested communities
Powered by