# Opening the editor for a specific node programmatically

**URL:** <https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724>\
**Category:** Developing Nodes\
**Created:** [18 August 2025 20:56 UTC](https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724 "2025-08-18T20:56:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![TacticalNudge](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@TacticalNudge](https://discourse.nodered.org/u/TacticalNudge)\
**Post date:** [18 August 2025 20:56 UTC](https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724/1 "2025-08-18T20:56:13Z")

</div>

Hi everyone.

I’ve got a case where we have a node editor containing an editableList. The first column of the editableList contains a dropdown / select of all the FooConfigNode instances This is easy enough to populate by filtering from `RED.nodes.eachConfig`, but I would also like to be able to create a FooConfigNode by adding a “Create New FooConfig“ button to the bottom of the editableList.Is there a way to trigger opening a new editor for the FooConfigNode type or maybe even opening the editor for a specific FooConfigNode instance? I had a look through `RED.editor...` but I suspect that this might be part of the undocumented API.

Any hints or tips that could point me in the right direction?

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [19 August 2025 10:04 UTC](https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724/2 "2025-08-19T10:04:20Z")

</div>

> [@TacticalNudge](#):
>
> I had a look through `RED.editor...` but I suspect that this might be part of the undocumented API.

That's right, you need to use `editConfig` with `_ADD_` as `id` to create a new config node.

> <https://github.com/GogoVega/node-red/blob/33d83d016a0c990c5aed208056d19f0e52913015/packages/node_modules/%40node-red/editor-client/types/index.d.ts#L2567>

---

<div class="post-metadata">

**Author:** ![AllanOricil](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/allanoricil/32/106911_2.png) [@AllanOricil](https://discourse.nodered.org/u/AllanOricil)\
**Post date:** [19 August 2025 20:40 UTC](https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724/3 "2025-08-19T20:40:17Z")

</div>

@TacticalNudge

I know it is not related to your issue but i would like to let you know i created a framework to write nodes and you could help finding issues if you develop your custom nodes using it

> **[GitHub - AllanOricil/node-red-vue-template: Write Node-RED nodes using Vue and Typescript](https://github.com/AllanOricil/node-red-vue-template)**
>
> Write Node-RED nodes using Vue and Typescript

It allows you to author nodes using current web dev tooling and use vue 3 to write your node forms. I need non biased people to try it and find issues that i cant see. There is no editableList vue component in the core yet, but you could add it with a PR in the above repo.

---

<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:** [18 October 2025 20:40 UTC](https://discourse.nodered.org/t/opening-the-editor-for-a-specific-node-programmatically/98724/4 "2025-10-18T20:40:19Z")

</div>

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