We are building agents that will have the same workflows but multiple credentials. For example, several clients needing to connect to their own Box.com accounts but use the same workflows.
Right now, it seems like the only way to address this is coping the workflow and then sending the client the link to the credentials.
I am curious how others are building this out and scaling?
Hi @Dale ,
It’s been some time since you asked this question, so I hope you have already figured that out.
But in case you didn’t here’s a possible solution:
Instead of letting n8n take care of the credentials, you can authenticate in your workflow. For example a HEADER auth sends the token in the header of the HTTP Request.
So you could add a header with the token when making that request, instead of selecting the credentials stored in n8n.
To store the credentials safely you would need to save them in a secure database, possibly encrypted. When running the execution for a certain client, you would retrieve his credentials from the database, unencrypt in n8n and run the execution.
That would mean the credentials would be visible in plain text for anyone who has access to the n8n executions.
To solve this security issue you could either be very careful with who you give access to your n8n or you could setup a very short period for storing the executions. They would quickly be deleted after that period.
To setup that check this link:
Does that clarify your question? If yes, please remember to mark my reply as a solution.