Problem connecting customer's Gmail account to my workflow

Describe the problem/error/question

I need to set up an automated Gmail workflow in n8n for a customer who uses their own Gmail account, but I don’t want to give them access to my n8n instance to prevent them from using my resources/runs. What is the best way to allow them to authorize access to Gmail once, while keeping everything running on my n8n without sharing the project? I can’t find any solution.

Information on your n8n setup

  • **n8n version:**Version 2.7.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows 11
1 Like

Hi @Samuele_Zunino Welcome to the community!
Consider reading this before moving further:


The most practical workaround without crossing the licensing aspect is to give clients their own instance or get them to pay for a new n8n instance with their credentials and you give them your workflow. I guess that is the most preferable workaround, else your approach would clearly cross boundaries of terms and conditions of n8n.

1 Like

schedule a video call (Zoom/Teams) and share your screen with “Remote Control” enabled. Open the Gmail credential modal on your n8n instance, then allow the client to take control of your mouse and keyboard to click “Sign in with Google” and enter their credentials directly. This ensures the OAuth token is generated on your server’s session while keeping their password private.

Basically, if you aren’t reselling access to the n8n editor or building a public hosting platform that competes with n8n Cloud, and you’re just keeping the use as a managed service where you sell the automation results (like processed leads or emails), then you are completely on the safe side.