# Feature Requests

**URL:** https://discourse.nodered.org/c/development/feature-requests/13.md?page=10

[Latest](https://discourse.nodered.org/latest.md) · [Categories](https://discourse.nodered.org/categories.md) · [Tags](https://discourse.nodered.org/tags.md)

**Page:** 11

---

## [\[Feature Request\]Allow one-liner JavaScript as well as JSONata](https://discourse.nodered.org/t/feature-request-allow-one-liner-javascript-as-well-as-jsonata/82825)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 46\
**Last updated:** [15 November 2023 19:06 UTC](https://discourse.nodered.org/t/feature-request-allow-one-liner-javascript-as-well-as-jsonata/82825 "2023-11-15T19:06:00Z")

</div>

JSONata main use in NR is to just perform a little manipulation of data to save having to write a function node But its syntax is not well understood by most of us (@E1cid is the exception ) whereas even I can google to…

---

## [Allow adding headers to WebSocket client?](https://discourse.nodered.org/t/allow-adding-headers-to-websocket-client/82842)

<div class="topic-metadata">

**Author:** [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Replies:** 9\
**Last updated:** [14 November 2023 21:22 UTC](https://discourse.nodered.org/t/allow-adding-headers-to-websocket-client/82842 "2023-11-14T21:22:21Z")

</div>

So... I have just needed to manually code up a web socket client function node, in order to pass custom headers (i.e bearer token) to a WebSocket server I was surprised this is not already allowed. As per guidelines, …

---

## [Node-red-node-serialport port selection](https://discourse.nodered.org/t/node-red-node-serialport-port-selection/82651)

<div class="topic-metadata">

**Author:** [@yhur](https://discourse.nodered.org/u/yhur)\
**Replies:** 18\
**Last updated:** [14 November 2023 06:43 UTC](https://discourse.nodered.org/t/node-red-node-serialport-port-selection/82651 "2023-11-14T06:43:04Z")

</div>

When the node-red starts, the flow(program) picks up the hard-coded serial ports and open them. But when a device re-connects after disconnecting for any reason, it may be possible the port number change, but the end use…

---

## [\[Feature Request\]Add ability to use JSONata and/or $Env in Change node](https://discourse.nodered.org/t/feature-request-add-ability-to-use-jsonata-and-or-env-in-change-node/82824)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 19\
**Last updated:** [13 November 2023 12:21 UTC](https://discourse.nodered.org/t/feature-request-add-ability-to-use-jsonata-and-or-env-in-change-node/82824 "2023-11-13T12:21:45Z")

</div>

I've recently been trying to make a flow work with parameters (instead of writing a function) but I can't use Change nodes this way The switch node alllows for JSONata and $env but not the change node

---

## [MQTT IN dynamic subscription mode add msg.qos](https://discourse.nodered.org/t/mqtt-in-dynamic-subscription-mode-add-msg-qos/82738)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 4\
**Last updated:** [9 November 2023 11:52 UTC](https://discourse.nodered.org/t/mqtt-in-dynamic-subscription-mode-add-msg-qos/82738 "2023-11-09T11:52:59Z")

</div>

Standard default is QoS2 set in node config but option not available in Dynamic mode and it turns out it still defaults to QoS 2 Even adding a change node before the MQTT IN node in dynamic mode and setting msg.qo…

---

## [Right click and drag mouse to move the design canvas](https://discourse.nodered.org/t/right-click-and-drag-mouse-to-move-the-design-canvas/82719)

<div class="topic-metadata">

**Author:** [@jacksonlancaster](https://discourse.nodered.org/u/jacksonlancaster)\
**Replies:** 0\
**Last updated:** [8 November 2023 15:28 UTC](https://discourse.nodered.org/t/right-click-and-drag-mouse-to-move-the-design-canvas/82719 "2023-11-08T15:28:24Z")

</div>

Make the canvas moveable by right clicking (and holding down the button) and dragging the mouse. Miro has a similar feature for reference.

---

## [\[Feature Request\]Put deploy at top of right-click menu](https://discourse.nodered.org/t/feature-request-put-deploy-at-top-of-right-click-menu/82466)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 7\
**Last updated:** [30 October 2023 16:37 UTC](https://discourse.nodered.org/t/feature-request-put-deploy-at-top-of-right-click-menu/82466 "2023-10-30T16:37:16Z")

</div>

It would save a LOT of wrist movement :slight\_smile:

---

## [Thoughts for a small enhancement - Editor browser tab title?](https://discourse.nodered.org/t/thoughts-for-a-small-enhancement-editor-browser-tab-title/82326)

<div class="topic-metadata">

**Author:** [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Replies:** 2\
**Last updated:** [25 October 2023 10:44 UTC](https://discourse.nodered.org/t/thoughts-for-a-small-enhancement-editor-browser-tab-title/82326 "2023-10-25T10:44:22Z")

</div>

Hi devs, A small thought - currently, the browser tab's title does not change when you change tabs in the Editor. Feels like this might be a useful enhancement? I noticed this when creating a note in my Obsidian noteb…

---

## [Changing node icons based on configuration](https://discourse.nodered.org/t/changing-node-icons-based-on-configuration/82280)

<div class="topic-metadata">

**Author:** [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Replies:** 4\
**Last updated:** [23 October 2023 19:42 UTC](https://discourse.nodered.org/t/changing-node-icons-based-on-configuration/82280 "2023-10-23T19:42:11Z")

</div>

I have been asked by a client if it is possible to make the node icon settable based on a configuration variable... so more dynamic (but only at edit/config time)... Currently we can set the icon based on a function - s…

---

## [Show a message in the log with \`postinstall\` script](https://discourse.nodered.org/t/show-a-message-in-the-log-with-postinstall-script/82164)

<div class="topic-metadata">

**Author:** [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Replies:** 3\
**Last updated:** [21 October 2023 09:20 UTC](https://discourse.nodered.org/t/show-a-message-in-the-log-with-postinstall-script/82164 "2023-10-21T09:20:49Z")

</div>

Hi all, I would like to display a message in the log after installation using the postinstall script but it seems that this is not natively possible (see \[BUG\] npm install does not run postinstall nor does it show name &…

---

## [Flow lock/unlock and show/hide permission](https://discourse.nodered.org/t/flow-lock-unlock-and-show-hide-permission/82219)

<div class="topic-metadata">

**Author:** [@BaptMB](https://discourse.nodered.org/u/BaptMB)\
**Replies:** 1\
**Last updated:** [20 October 2023 13:09 UTC](https://discourse.nodered.org/t/flow-lock-unlock-and-show-hide-permission/82219 "2023-10-20T13:09:56Z")

</div>

Hello, Following version 3.1 that can lock and unlock flow. It would be great if we can have a specific permission/authorization for that property as well as flow visibility. This allow, at low cost, to have 2 levels o…

---

## [Feature Request / Potential PR: Allow plugins (that don't include nodes) to be managed by the palette manager](https://discourse.nodered.org/t/feature-request-potential-pr-allow-plugins-that-dont-include-nodes-to-be-managed-by-the-palette-manager/80447)

<div class="topic-metadata">

**Author:** [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Replies:** 4\
**Last updated:** [18 October 2023 19:19 UTC](https://discourse.nodered.org/t/feature-request-potential-pr-allow-plugins-that-dont-include-nodes-to-be-managed-by-the-palette-manager/80447 "2023-10-18T19:19:08Z")

</div>

Continuing the discussion from Some nodes not showing in 'Manage palette': I stumbled - once again - over the fact that a plugin without nodes isn't shown in the Palette Manager; thus, despite the plugin can be install…

---

## [\[Feature Request\]Delete nodes by dragging back to left side bar](https://discourse.nodered.org/t/feature-request-delete-nodes-by-dragging-back-to-left-side-bar/81992)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 9\
**Last updated:** [13 October 2023 12:29 UTC](https://discourse.nodered.org/t/feature-request-delete-nodes-by-dragging-back-to-left-side-bar/81992 "2023-10-13T12:29:11Z")

</div>

In all other block programming editors (Scratch, Snap!, Blocky etc), they all allow you to delete a loose block by dragging it back over to the left hand palette. This catches me out in Node-RED, as I repeatably try to …

---

## [Rate limiting with delay node](https://discourse.nodered.org/t/rate-limiting-with-delay-node/81809)

<div class="topic-metadata">

**Author:** [@HaroldPetersInskipp](https://discourse.nodered.org/u/HaroldPetersInskipp)\
**Replies:** 0\
**Last updated:** [5 October 2023 17:33 UTC](https://discourse.nodered.org/t/rate-limiting-with-delay-node/81809 "2023-10-05T17:33:04Z")

</div>

I couldn't find a sufficient option for a recent Karaoke project. What I needed was the ability to send the first X messages in Y time period and then drop the rest until the time is up. I ended up using a function node…

---

## [Indication Icon for Nodes where a description text is entered](https://discourse.nodered.org/t/indication-icon-for-nodes-where-a-description-text-is-entered/81736)

<div class="topic-metadata">

**Author:** [@Martin12](https://discourse.nodered.org/u/Martin12)\
**Replies:** 4\
**Last updated:** [3 October 2023 10:39 UTC](https://discourse.nodered.org/t/indication-icon-for-nodes-where-a-description-text-is-entered/81736 "2023-10-03T10:39:47Z")

</div>

Not sure if this is the right place to suggest something but I think its better to do it here than nowhere :slight\_smile: When creating more complex nodes, especially function nodes with own code, it is such a handy fea…

---

## [Another option for DEBUG nodes](https://discourse.nodered.org/t/another-option-for-debug-nodes/81734)

<div class="topic-metadata">

**Author:** [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Replies:** 0\
**Last updated:** [3 October 2023 03:22 UTC](https://discourse.nodered.org/t/another-option-for-debug-nodes/81734 "2023-10-03T03:22:20Z")

</div>

It is nice that you are able to control how the debug nodes are output to the right side of the screen. You can have all, flow and selected. Which is a very good selection. flow is the one I use a lot of the time, as …

---

## [Include ip-address in logs for type audit](https://discourse.nodered.org/t/include-ip-address-in-logs-for-type-audit/81724)

<div class="topic-metadata">

**Author:** [@khfischbach](https://discourse.nodered.org/u/khfischbach)\
**Replies:** 1\
**Last updated:** [2 October 2023 20:03 UTC](https://discourse.nodered.org/t/include-ip-address-in-logs-for-type-audit/81724 "2023-10-02T20:03:16Z")

</div>

I found in the logfile for a successfull login: 2 Oct 15:04:27 - \[audit\] {"event":"auth.login.revoke","level":98,"user":{"username":"abcd","permissions":"\*"},"path":"/auth/revo ke","ip":"192.xxx.xxx.xxx","timestamp"…

---

## [Disable/Enable a group](https://discourse.nodered.org/t/disable-enable-a-group/81712)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 5\
**Last updated:** [2 October 2023 14:00 UTC](https://discourse.nodered.org/t/disable-enable-a-group/81712 "2023-10-02T14:00:26Z")

</div>

I've found myself a few times recently wanting to disable/enable all the nodes in a group Could this be added to the nice to have list please? :slight\_smile: On the right-click group context menu :slight\_smile:

---

## [Fix Node-RED URL case sensitivity for http-in/-out](https://discourse.nodered.org/t/fix-node-red-url-case-sensitivity-for-http-in-out/81688)

<div class="topic-metadata">

**Author:** [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Replies:** 2\
**Last updated:** [1 October 2023 10:58 UTC](https://discourse.nodered.org/t/fix-node-red-url-case-sensitivity-for-http-in-out/81688 "2023-10-01T10:58:37Z")

</div>

Hi devs. Following this discussion: Uibuilder and URL case sensitivity - General - Node-RED Forum (nodered.org), @annuello spotted that Node-RED does not follow the W3C guidelines on the use of case sensitivity in URL's…

---

## [Prevent duplicate imports by name into config nodes](https://discourse.nodered.org/t/prevent-duplicate-imports-by-name-into-config-nodes/81314)

<div class="topic-metadata">

**Author:** [@malee](https://discourse.nodered.org/u/malee)\
**Replies:** 0\
**Last updated:** [14 September 2023 14:47 UTC](https://discourse.nodered.org/t/prevent-duplicate-imports-by-name-into-config-nodes/81314 "2023-09-14T14:47:18Z")

</div>

Hi Node-RED, When importing nodes or examples into flows and when these imports contain settings for configuration nodes duplicate entries with the same name are created. This is for the same configuration node type. I…

---

## [Node multiple in/out for better flow structure](https://discourse.nodered.org/t/node-multiple-in-out-for-better-flow-structure/81115)

<div class="topic-metadata">

**Author:** [@stone](https://discourse.nodered.org/u/stone)\
**Replies:** 5\
**Last updated:** [9 September 2023 14:18 UTC](https://discourse.nodered.org/t/node-multiple-in-out-for-better-flow-structure/81115 "2023-09-09T14:18:55Z")

</div>

so here is my proposal: add top and bottom in/out to ALL nodes. --if the node has a left side in, then it should have a top side in as well. --if the node has a right side out, then it should have a bottom side out …

---

## [Navigating between flows](https://discourse.nodered.org/t/navigating-between-flows/81141)

<div class="topic-metadata">

**Author:** [@duaw](https://discourse.nodered.org/u/duaw)\
**Replies:** 4\
**Last updated:** [9 September 2023 13:31 UTC](https://discourse.nodered.org/t/navigating-between-flows/81141 "2023-09-09T13:31:40Z")

</div>

Hi there! Each flow populates a tab in the browser. With many flows, the list at the top gets longer and longer. Most time the tar bar is not long enough: Only a fraction of all flows is visible at a time. Searching & …

---

## [Un-deprecate "string or buffer" autodetection in mqtt-in node](https://discourse.nodered.org/t/un-deprecate-string-or-buffer-autodetection-in-mqtt-in-node/80897)

<div class="topic-metadata">

**Author:** [@AndreKR](https://discourse.nodered.org/u/AndreKR)\
**Replies:** 7\
**Last updated:** [30 August 2023 13:51 UTC](https://discourse.nodered.org/t/un-deprecate-string-or-buffer-autodetection-in-mqtt-in-node/80897 "2023-08-30T13:51:11Z")

</div>

In MQTT in node auto-detect mode should include trying to parse JSON · Issue #3410 · node-red/node-red · GitHub (by @dceejay and @knolleary) the ability to auto-detect and parse JSON in an MQTT message was added. At the …

---

## [Ignore SSL issues in "Feedparser" node](https://discourse.nodered.org/t/ignore-ssl-issues-in-feedparser-node/80879)

<div class="topic-metadata">

**Author:** [@fagnes](https://discourse.nodered.org/u/fagnes)\
**Replies:** 0\
**Last updated:** [29 August 2023 08:52 UTC](https://discourse.nodered.org/t/ignore-ssl-issues-in-feedparser-node/80879 "2023-08-29T08:52:00Z")

</div>

It is impossible now to fetch RSS-feeds from site with "problem" certificate (self-signed for example). Could you please add an option to ignore such errors?

---

## [QoL - Deleting junction with only 1:1 (should) result in wires connecting the nodes](https://discourse.nodered.org/t/qol-deleting-junction-with-only-1-1-should-result-in-wires-connecting-the-nodes/80792)

<div class="topic-metadata">

**Author:** [@deisele](https://discourse.nodered.org/u/deisele)\
**Replies:** 2\
**Last updated:** [25 August 2023 10:48 UTC](https://discourse.nodered.org/t/qol-deleting-junction-with-only-1-1-should-result-in-wires-connecting-the-nodes/80792 "2023-08-25T10:48:04Z")

</div>

Hi, I use junctions at some places to clean up the wiring for better readability. When deleting them I have to rewire in many cases (IMHO) "unnecessarily", where I just want to remove the junction but want to keep the …

---

## [\[Feature Request\] Node Status translation context](https://discourse.nodered.org/t/feature-request-node-status-translation-context/80368)

<div class="topic-metadata">

**Author:** [@lutz](https://discourse.nodered.org/u/lutz)\
**Replies:** 0\
**Last updated:** [7 August 2023 09:24 UTC](https://discourse.nodered.org/t/feature-request-node-status-translation-context/80368 "2023-08-07T09:24:15Z")

</div>

Hi all, I'm trying to use translation with context on a node's status. Due to the fact that RED.\_('translate-text', context) is getting evaluated in backend without information about the clients languages, the translate…

---

## [\[Feature request\] Add something (icon, border, ...) to nodes that have a description written by the developer](https://discourse.nodered.org/t/feature-request-add-something-icon-border-to-nodes-that-have-a-description-written-by-the-developer/79962)

<div class="topic-metadata">

**Author:** [@fruityfred](https://discourse.nodered.org/u/fruityfred)\
**Replies:** 4\
**Last updated:** [22 July 2023 19:47 UTC](https://discourse.nodered.org/t/feature-request-add-something-icon-border-to-nodes-that-have-a-description-written-by-the-developer/79962 "2023-07-22T19:47:17Z")

</div>

This would allow developers to instantly see all the nodes where a description has been written.

---

## [Named access to flows with the Admin HTTP API](https://discourse.nodered.org/t/named-access-to-flows-with-the-admin-http-api/79933)

<div class="topic-metadata">

**Author:** [@Lanti](https://discourse.nodered.org/u/Lanti)\
**Replies:** 0\
**Last updated:** [19 July 2023 11:21 UTC](https://discourse.nodered.org/t/named-access-to-flows-with-the-admin-http-api/79933 "2023-07-19T11:21:57Z")

</div>

I'm closely following this documentation to control Node-red with HTTP API. Maybe I'm not understand fully how it works, but I can only target flows, subflows by their ID? This is problematic, because if I want to create…

---

## [\[Feature Request\]Little tweak on wires](https://discourse.nodered.org/t/feature-request-little-tweak-on-wires/79336)

<div class="topic-metadata">

**Author:** [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Replies:** 20\
**Last updated:** [16 July 2023 19:41 UTC](https://discourse.nodered.org/t/feature-request-little-tweak-on-wires/79336 "2023-07-16T19:41:44Z")

</div>

I'm just wondering if a little tweak could be made to the wire routing just to put a gap between the wires and node statuses when looping back from right top left \[edit\] Don't need as much room as this workaround - …

---

## [Restarting single flow does not work, restarts the whole instance](https://discourse.nodered.org/t/restarting-single-flow-does-not-work-restarts-the-whole-instance/79487)

<div class="topic-metadata">

**Author:** [@milkbaconleopardveal](https://discourse.nodered.org/u/milkbaconleopardveal)\
**Replies:** 3\
**Last updated:** [1 July 2023 08:24 UTC](https://discourse.nodered.org/t/restarting-single-flow-does-not-work-restarts-the-whole-instance/79487 "2023-07-01T08:24:06Z")

</div>

Hello there, I am running Node-RED 3.0.2 in a dockerized environment on Ubuntu 20.04 and I am using the API to restart the flows, only to discover that by calling the API from the istance itself it restarts the whole in…

[Previous page](https://discourse.nodered.org/c/development/feature-requests/13.md?page=9)

[Next page](https://discourse.nodered.org/c/development/feature-requests/13.md?page=11)