# Optional "keywords" on node definitions for palette filter and quick-add

**URL:** <https://discourse.nodered.org/t/optional-keywords-on-node-definitions-for-palette-filter-and-quick-add/102107>\
**Category:** Feature Requests\
**Created:** [9 November 2026 11:19 UTC](https://discourse.nodered.org/t/optional-keywords-on-node-definitions-for-palette-filter-and-quick-add/102107 "2026-11-09T11:19:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dirkjanfaber](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dirkjanfaber/32/46291_2.png) [@dirkjanfaber](https://discourse.nodered.org/u/dirkjanfaber)\
**Post date:** [9 November 2026 11:19 UTC](https://discourse.nodered.org/t/optional-keywords-on-node-definitions-for-palette-filter-and-quick-add/102107/1 "2026-11-09T11:19:19Z")

</div>

Hi all,

I mentioned this to Nick a while ago, so here it is properly.

The palette filter and the quick-add dialog only match a node's type and label. That makes nodes hard to find when users search for the product they own rather than the generic node name. Our example: the Victron Energy Switch node handles several switching products (GX IO-Extender, the new Koro 640 GX S with its Aurelia DC distribution, virtual switches). Users search for "koro" or "aurelia" and get no results.

While searching the forum I came across an older thread asking for the same thing: [Extending the search box](https://discourse.nodered.org/t/extending-the-search-box/4388). There, searching the node help was considered too noisy (common words like "input" would match everything), and a tag list was suggested as a backwards compatible alternative. My proposal is along those lines.

Not to be confused with package.json keywords: the palette manager's Install tab already searches those (see [Pallette keywords - #5 by BartButenaers](https://discourse.nodered.org/t/pallette-keywords/570/5)). This is about finding an installed node in the palette filter and quick-add, per node rather than per package.

Proposal: an optional keywords array in RED.nodes.registerType:

```auto
    RED.nodes.registerType('victron-input-switch', {
        category: 'Victron Energy',
        paletteLabel: 'Switch',
        keywords: ['Koro', 'Aurelia', 'IO-Extender'],
        ...
    })

```

The palette filter and quick-add would match these in addition to type and label. No UI change, nodes without keywords behave as before, and older Node-RED versions ignore the field, so nodes can add it straight away.

I have a working change against dev (`palette.js` and `typeSearch.js`, about 10 lines) and am happy to open a PR if this fits your plans:

> **[Comparing node-red:main...dirkjanfaber:feat/node-keywords-search ·...](https://github.com/node-red/node-red/compare/main...dirkjanfaber:node-red:feat/node-keywords-search)**
>
> Low-code programming for event-driven applications - Comparing node-red:main...dirkjanfaber:feat/node-keywords-search · node-red/node-red

Best,  
Dirk-Jan

---

<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:** [9 November 2026 11:28 UTC](https://discourse.nodered.org/t/optional-keywords-on-node-definitions-for-palette-filter-and-quick-add/102107/2 "2026-11-09T11:28:27Z")

</div>

Hi @dirkjanfaber

Please do raise the PR - much easier to review and discuss with working code in front of us.

Regards,  
Nick

---

<div class="post-metadata">

**Author:** ![dirkjanfaber](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dirkjanfaber/32/46291_2.png) [@dirkjanfaber](https://discourse.nodered.org/u/dirkjanfaber)\
**Post date:** [9 November 2026 12:11 UTC](https://discourse.nodered.org/t/optional-keywords-on-node-definitions-for-palette-filter-and-quick-add/102107/3 "2026-11-09T12:11:08Z")

</div>

Sure! I've created one [here](https://github.com/node-red/node-red/pull/6079).