Peter - Hi everyone,I have a self-hosted n8n ...
Hi everyone,
I have a self-hosted n8n instance where I manage automation workflows for multiple clients.
I'm curious how agencies handle Google OAuth onboarding for Google Calendar and Google Sheets.
Do you give clients temporary remote access (AnyDesk, RustDesk, Zoom, etc.) so they can click "Sign in with Google" and authorize their own account?
Or do you give clients access to the n8n editor to connect their credentials themselves?
If you give editor access, how do you do that securely when a single n8n instance contains workflows for many different clients? How do you prevent clients from seeing or accessing other clients' workflows?
Or do you use a completely different approach?
I'd love to know the common production workflow used by agencies managing multiple clients on a single self-hosted n8n instance. Thanks!
I have a self-hosted n8n instance where I manage automation workflows for multiple clients.
I'm curious how agencies handle Google OAuth onboarding for Google Calendar and Google Sheets.
Do you give clients temporary remote access (AnyDesk, RustDesk, Zoom, etc.) so they can click "Sign in with Google" and authorize their own account?
Or do you give clients access to the n8n editor to connect their credentials themselves?
If you give editor access, how do you do that securely when a single n8n instance contains workflows for many different clients? How do you prevent clients from seeing or accessing other clients' workflows?
Or do you use a completely different approach?
I'd love to know the common production workflow used by agencies managing multiple clients on a single self-hosted n8n instance. Thanks!
