I have a situation where I need to make multiple (6) HTTP POST requests to exactly the same URL but with different credentials. This is due to a multi-client situation I can’t control.
The immediate thing that comes to mind is to simply repeat the HTTP request the 6 times I need to POST but this looks a little weird on the workflow.
Am I missing a better way? credentials are stored in credentials, not the workflow (I’m not permitted to store them in the workflow itself).
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hi @KevinG
Thanks for posting here and welcome to the community! 
What kind of credentials do you have to use? What do you mean by “multi-client” ?
If they are generic you can actually use expressions in the credentials and therefore either reference some custom variables you have set up (or better yet, use secrets) or you can create a reference to within the workflow that runs with these credentials (with something like this {{ $input.item.json.user }}. They will then be evaluated at runtime of the workflow execution.
Example:
You could then make the credential provision a little more dynamic in your workflow.
Please note, that it’s still the most save to have each credential set up separately and then used with 6 separate calls (like your original approach).
Also, please bear in mind that the n8n license has some restrictions to this. If you were using multiple users credentials to connect to a service you don’t own, you may need an embed license.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
