Reusable flows with different credentials (parameteraize/ programatically)

[David_Ho]

Reusable flows with different credentials.

We need to support a lot of customers (embbeding), with a lot of different flow.
Each customer (B2B) have his own credentials.

We need a secured way to run a flow only for specific customer. the current state of the platform is that we need to create a flow for each customer. this can be hundreds.
we also update and upgrade flows.

The current state of N8N is that you need to create flow for each customer which is a huge overload to develop such a thing, upgrade is also huge and tragic event.
Using expressions is not secured at all since you can see the credentials more than that there are way too many ways to use it : Oauth2/ ApiKey, etc…

I saw way too many tickets that have so many votes for this feature, but it seems like it is ignored.

Select credentials via expression

Hi, When creating an HTTP Request node, I would like to be able to dynamically select the credentials set to use based on an expression. It is not exactly as Access saved credentials from "expressions" as I don’t really need to access the credentials itself but only to tell HTTP Request node which credentials to use. My use case: I have 3 environments (dev, test, prod) When an event is detected on any of these envs, it triggers a n8n webhook. The payload contains the environment. A unique wo…

Allow expression for credential selection

The idea is: At the moment we can use expressions within the setup of credentials. But I would like to use an expression to set the ID of the credentials, this would allow flexibility without having the credentials visible within the workflow and executions. so instead of [image] to something like this: [image] My use case: Currently I am creating workflows to scrape Workflow and Execution data from multiple environments. Having URL and API key visible in the executions / workflow data is…

How to use Expressions for Credentials in HTTP Request node?

Describe the problem/error/question I have a workflow which runs though several URLs, each URL has its own Header Auth. How can I program the HTTP Request node to use a specific Auth for the specific URL using Expression? Please share your workflow

I don’t want to add more links since the team is already aware for that.

Today we are in the middle of examining the platform with license for (embedded + enterprise) vs competitors, we like the platform but this feature is a must for us, otherwise its a huge overload on RnD team. I know some other platforms don’t support it too, some does support it and we examined them too.

Is this feature gonna be implemented soon? or neglected? (feature requests made from 2020 already)

[Sow_B]

I also need this but they way people request a solution above is bad and won’t work and possibly why it hasn’t been implemented yet… We shouldn’t allow ‘dynamic’ selection of credentials, instead I feel the best way to implement is as follows -

In the enterprise licence we can already create ‘projects’ which has their own ‘credentials’ for each ‘project’ - this is great and useful. We can replicate our master flow into each of these projects

THEN we introduce ‘local’ variables to each project - this is like global variables but only seen within the project and not to others. Local variables can be called the same thing like $myVar1 and used through any flow within the project.

THEN we create another master flow where we can do upgrades and enhancements and use the same variable of $myVar1 and once we copy and paste that flow into the project then the flow uses the local variables of the project.

This will mean that you can upgrade any flow and then copy and paste to deploy it on any project and it won’t break anything. It’s easy to maintain.

[Jon]

Morning,

I was chatting to one of our product managers about this earlier this week and he may be about to pick up using expressions to dynamically select credentials to use in a workflow which would solve most of these requests.

[David_Ho]

@Jon

I was chatting to one of our product managers about this earlier this week and he may be about to pick up using expressions to dynamically select credentials to use in a workflow which would solve most of these requests.

Thanks Jon for the update. Though as part of our needs we moved to other solution. If you had it we might have chosen your solution cause we really liked that it is open source and deployable on K8S, also the SSO using SAML.

[Jon]

Hey @David_Ho,

That is understandable, It takes time to pick up some features and they need a lot of ground work.

Maybe in the future once this has been implemented you can check it out again, One thing I would note is while our source is available it isn’t “open source”. Out of interest can you share what you went with in the end?

[pemontto]

This is something I’ve discussed before, and what I thought the Vars feature was going to be.

Effectively like env vars in a unix context, depending on which file you choose/vars you load dictates what values are used. E.g. dev/prod etc.