Multi-tenant SaaS + Google nodes: how to use per-user OAuth tokens (dynamic credentials)?

[Alexandre_P]

The idea is:

Allow dynamic credential selection at execution time, or allow native Google nodes (Gmail / Google Calendar) to accept externally-issued OAuth tokens (access + refresh) instead of requiring a statically selected n8n credential.

My use case:

I’ve built for clients multiple multi-tenant SaaS where AI agents CRUD Gmail and Google Calendar on behalf of end users.
OAuth is handled outside n8n (via Clerk), so for each execution I already have:

• access_token
• refresh_token
• expiry info
• any other info needed
  However, n8n’s Gmail / Google Calendar nodes require a credential selected at design time, which makes them unusable in this setup.
  As a result, I’m forced to:
• Replace native nodes with HTTP Request
• Manually manage headers, token refresh, retries, edge cases
• Duplicate logic that native nodes already handle better
  This comes up repeatedly across different projects.

I think it would be beneficial to add this because:

• This is a hard blocker for SaaS / multi-tenant architectures
• Native nodes become effectively single-tenant
• Workarounds are:
  • brittle
  • time-consuming
  • less secure if users try to hack around credential storage
• Other automation platforms explicitly support “run with user token” patterns
  Supporting dynamic credentials would:
• unlock serious SaaS use cases
• reduce HTTP-node spaghetti
• encourage best practices instead of hacks
• significantly improve reusability of workflows

Any resources to support this?

Loads of conversation around this on the forum

Best Practices on Dynamic Credentials?

Hey guys, I know N8N doesn’t natively support dynamic credentials out of the box and there are a number workarounds I’ve seen people apply. I’m curious to hear the communities perspective on the best way to do this and any resources that might be helpful to solve this problem. I have a SAAS I’ve been building for sometime now. I have a multi-factor authentication all set-up within the app and have a chatbot. I’d like to connect the chatbot to N8N and run it through some multi-agents I’ve built…

Using n8n API to build a SaaS with per-customer Google credentials – best practices?

Hi everyone, I’m currently building a SaaS platform on top of n8n and I’m running into challenges around Google integrations and multi-tenant credential management. I’d really appreciate feedback from anyone who has already built something similar. Project context: Users of my platform can buy prebuilt AI agents Each agent is defined by a JSON model with variables User-provided values are injected to generate a custom JSON This JSON is then sent to the n8n REST API to programmatica…

Dynamic Credential Selection via Expressions for Multi-Tenant Workflows

<!- Problem Statement Currently, credentials in n8n nodes must be selected statically at design time. This creates a major scalability issue for multi-tenant workflows where you need to interact with the same service (e.g., Google Calendar, Outlook, Gmail) using different credentials for different users/partners. (This issue is a generalization of: Seeking Advice on Implementing Dynamic Google Calendar Credentials for Multi-User Workflows in n8n - #2 by solomon ) Real-Wor…

Possible to do multi-tenant workflows that can reference credentials dynamically?

that is not the link to the NPM page. I made the github page private, that is why you cannot see it.

Select credentials via expression

Hi, I’d like to thank you for the community node. One question: would it be possible to use it with the chat model connected to the AI Agent?

How to use email nodes with multiple different credentials?

Solving Multi-User OAuth in n8n: A Complete Guide to Dynamic Credentials How to build scalable, secure OAuth credential management for multi-tenant n8n workflows If you’ve ever tried to build a SaaS application or multi-user automation platform with n8n, you’ve probably hit this wall: how do you handle different users’ credentials dynamically? n8n’s credential system works great for single-user scenarios, but when you need user-specific API access tokens that refresh automatically, things get…

Are you willing to work on this?

Yeah, not sure if I have the qualification, but with some help, I can try to start the work on it. Although this seems like a critical component so I’m pretty sure it needs a senior/principal dev on it.

[Ocade_Fusion]

This is a real game changer for multi-tenant SaaS: being able to inject dynamic OAuth tokens into Google nodes simplifies everything, no more hacky HTTP workarounds. It would be a huge leap in scalability and reliability, but it requires a senior dev to do it right.

Summary

• Problem: static OAuth tokens limit multi-tenant workflow scalability
• Solution: support dynamic credentials in Google nodes
• Benefits: elegant automation, fewer hacks, better reliability
• Challenge: needs a senior dev to fix properly

[Alexandre_P]

Don’t forget to vote for the feature request !

[Ocade_Fusion]

Thanks for the reminder, totally slipped my mind. Voted!

Valentin, Ocade Fusion