I’m exploring the possibility of implementing a multi-user setup with dynamic Google Calendar credentials in n8n. My goal is to allow different users to authorize their Google accounts so that actions in Google Calendar can be performed under each user’s credentials. However, I understand that n8n doesn’t natively support dynamic credential switching within a single workflow. I’m curious if anyone has tackled a similar challenge or if there are best practices or existing solutions to achieve this.
What is the error message (if any)?
There isn’t a specific error message, but rather a limitation in n8n’s ability to dynamically switch credentials within a single workflow.
Please share your workflow
(Currently, this is a conceptual setup. I'm still in the research phase and have not developed a specific workflow that can be shared yet.)
Share the output returned by the last node
N/A - Seeking initial guidance on implementing a multi-user approach.
Any advice, insights, or resource links would be greatly appreciated. Thank you!
I don’t know any methods of dynamic credentials using the default nodes, but it is possible using the HTTP Request node. This means you would have to read the API documentation to build the requests manually.
This would allow to handle the credentials dynamically, but they wouldn’t be encrypted anymore. Anyone with access to your workflow executions would be able to see the credentials.
But if you want to use the default nodes, a SWITCH node could work, like this:
For each CREATE, UPDATE or DELETE event in Google, you would have to use this logic.
If my reply answers your question, please remember to mark it as the solution.
i already success implementing this dynamic google auth for gmail, calendar and all google things, the concept is you must send link to user can login to their google account and then we save access_token in database. just set scope for other google product in the link.