# Do not add more than one config of the same type

**URL:** <https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314>\
**Category:** General\
**Created:** [26 November 2021 08:35 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314 "2021-11-26T08:35:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sercancetin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sercancetin/32/50083_2.png) [@sercancetin](https://discourse.nodered.org/u/sercancetin)\
**Post date:** [26 November 2021 08:35 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314/1 "2021-11-26T08:35:34Z")

</div>

Hello my dear masters. As seen in the picture, after adding a config node, no other option to add will appear, if the first node is deleted, the addition will be active. Is there a way to do this?

 ![Screenshot_1](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/f/1f37828133480749e705d31a90eb07d6e9de1cd0.png)

---

<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 November 2021 09:04 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314/3 "2021-11-26T09:04:32Z")

</div>

Hi @sercancetin

No, there is no way to limit it to only allow a single config node to be created.

There is a mode that requires each flow node to have its own config node, but that isn't what you're asking for.

---

<div class="post-metadata">

**Author:** ![sercancetin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sercancetin/32/50083_2.png) [@sercancetin](https://discourse.nodered.org/u/sercancetin)\
**Post date:** [26 November 2021 10:58 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314/4 "2021-11-26T10:58:20Z")

</div>

So what is that option? Have an example? Thank you for your interest.

---

<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 November 2021 11:05 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314/5 "2021-11-26T11:05:22Z")

</div>

It isn't a documented feature - so I'd be wary of recommending it as it isn't very well exercised.

But you can see it in action with the `node-red-node-swagger` set of nodes. They allow you to add API documentation to the HTTP In nodes. But each HTTP In node must have its own swagger doc node.

It is enabled by setting the `exclusive` flag on the config node definition.

> <https://github.com/node-red/node-red-node-swagger/blob/master/swagger/swagger.html#L86>

The editor then allows you to only create/delete a single config node for each consuming node

---

<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:** [25 January 2022 11:06 UTC](https://discourse.nodered.org/t/do-not-add-more-than-one-config-of-the-same-type/54314/6 "2022-01-25T11:06:24Z")

</div>

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