I has viewed the forum why-dont-node-red-nodes-allow-multiple-inputs.
And I have some different perspectives about multiple inputs in subflow node.
In an example like the one below,multiple inputs will be more convenient.
Messages are passed 1 by 1 and you will have to capture the input in order to deal with the messages.
The 'do something same' function handles them 1 by 1, never together, thus, having an additional input does not help.
Use a switch node to route the message and a join node to combine multiple messages and then process it. Or use context to store/read to combine multiple (more complex)
1 Like
Welcome to the forums @wenbei
This topic has been brought up so many times.
It doesn't matter where multiple input support is added - the mechanics behind it, are just to great, and will require a complete overhaul of message handling throughout the core of Node RED.
The topic property, along with a switch as @bakman2 mentions is what you need to use.
Got it.Thanks for your reply！
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
