n8n flaws · AI Automation Society

n8n flaws

Hey everone

Generally I love n8n, but there are some in my opinion very basic flaws of the node system and they kind of defy the whole point of a low-code environment if I end up scripting everything anyways.

One of the most prominent examples for me would be:

In n8n, if i have two parallel flows after a switch, how do I elegantly wait again for both afterwards, even if one of the outputs doesn't have any items? a) There's no way to have an empty item output for the routing option that has no items. a) The merge node doesn't continue if one input never arrives. c) I don't want to hardcode a timer and the wait node does not feature a 'wait for both inputs'. d) if I just route both into the next node, each input will trigger an independent continue of the flow. e) the 'execute only once' is something different entirely.

Does anyone know how to do this properly? I want to be able to execute things "in parallel" (knowing its not really parallel execution of course) but then later use combined data from different optional parallel flows later down the line.

Best,

Stefan

3 comments