I’m using n8n version 1.103 on a self-hosted Kubernetes environment and looking for best practices or official guidance on implementing multi-user OAuth within a workflow.
My goal:
Allow each user to authenticate with their own OAuth account as part of the workflow, without requiring a new credential entry to be saved in the n8n credentials system for each individual user.
Context:
I have reviewed documentation and community discussions and it appears n8n’s credential system requires a separate credential per OAuth-using user. However, I would like to confirm if there is a recommended or officially supported method to handle this scenario:
- Multi-user (SaaS/multi-tenant) workflow.
- Each user brings their own OAuth account (e.g., Google Calendar).
- Tokens are managed dynamically, ideally without storing a new n8n credential per user.
If direct dynamic credential input (per workflow execution, session, or input variable) is not available, are there any established patterns, upcoming features, or best practices for this use case (such as leveraging an external token broker/service)?
Is there any way to leverage embedded n8n or the REST API for automated credential management in this context?
Any advice or reference examples for implementing true multi-user OAuth in n8n workflows would be greatly appreciated!
Information on my n8n setup
- n8n version: 1.103
- Database postgres
- Running n8n via (Docker, npm, n8n cloud, desktop app): Kubernetes (self-hosted)