# How to configure "config" properties for a subflow

**URL:** https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274
**Category:** General
**Created:** [26 January 2022 16:14 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274 "2022-01-26T16:14:25Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![thib3113](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thib3113/32/55033_2.png) [@thib3113](https://discourse.nodered.org/u/thib3113)
#### Post date: [26 January 2022 16:14 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/1 "2022-01-26T16:14:25Z")

</div>

Hello all,

I'm trying to create some subflow for my new node .

My problem was, one of my node need a "config" property (a global configuration node) .  
Can I use this configuration node in the subflow properties ?

I didn't find how to do, and I need to go in the subflow to configure it manually (and so, the subflow is nearly useless because not always reusable) .

I try to do some search on the forum and documentation about it, but I doesn't find a way to do it for the moment .

Thanks  
PS : I'm using node-red v2.2.0-beta.1-git

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [26 January 2022 17:21 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/2 "2022-01-26T17:21:49Z")

</div>

This is not possible to do today. It has been mentioned a couple times recently, but nothing has happened with it.

---

<div class="post-metadata">

### Author: ![thib3113](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thib3113/32/55033_2.png) [@thib3113](https://discourse.nodered.org/u/thib3113)
#### Post date: [26 January 2022 18:29 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/3 "2022-01-26T18:29:17Z")

</div>

oh ...

Any workaround ?

Maybe a previous node to setup this in a variables ? (or maybe in a message send to the subflow, and the subflow can store it only for the subflow ? maybe in the flow var ? )

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [26 January 2022 19:28 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/4 "2022-01-26T19:28:11Z")

</div>

No. Subflow env vars are evaluated and set at deploy time. They cannot be set msg properties.

Likewise, there's no way in the UI for you to tell a node to use an env var to identify the config node it should be using.

---

<div class="post-metadata">

### Author: ![thib3113](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thib3113/32/55033_2.png) [@thib3113](https://discourse.nodered.org/u/thib3113)
#### Post date: [26 January 2022 21:42 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/5 "2022-01-26T21:42:48Z")

</div>

In fact, I'm thinking in term of code ...

Like creating "specifics nodes" that will convert the config to ID string in message (because it's just an id in the code), and at the start of the subflow, another specific node, that will look at the message, and setup a "flow var" (I'm pretty news with node-red, so I doesn't know what are the scope of the global vars)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [27 March 2022 21:43 UTC](https://discourse.nodered.org/t/how-to-configure-config-properties-for-a-subflow/57274/6 "2022-03-27T21:43:21Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
