# Create a new node with multiple inputs directly?

**URL:** <https://discourse.nodered.org/t/create-a-new-node-with-multiple-inputs-directly/15878>\
**Category:** Developing Nodes\
**Created:** [25 September 2019 08:19 UTC](https://discourse.nodered.org/t/create-a-new-node-with-multiple-inputs-directly/15878 "2019-09-25T08:19:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [25 September 2019 09:23 UTC](https://discourse.nodered.org/t/create-a-new-node-with-multiple-inputs-directly/15878/5 "2019-09-25T09:23:39Z")

</div>

Supporting only one input was a fundamental design choice (and a good one, IMO), otherwise the flow engine would have to be _a lot_ more complex.

There was a nice discussion about this topic a while ago here:

> [@Why don't Node-RED nodes allow multiple inputs?](https://discourse.nodered.org/t/why-dont-node-red-nodes-allow-multiple-inputs/10973):
>
> For clarity: I'm not asking how to implement multiple inputs to a function, I already know the workarounds. I want to know why Node-RED developers would inhibit such a functionality. It seems so obvious and natural to allow multiple inputs to a function. For example: say I want to create a function Divide(dividend, divisor) that returns dividend divided by divisor. In JavaScript this would be: function Divide(dividend, divisor) { return dividend / divisor } With Node-RED, the same functio…

---

_[View the full topic](https://discourse.nodered.org/t/create-a-new-node-with-multiple-inputs-directly/15878)._