Neither please god. We used Node-Red at a previous job for integrating some third party software, total disaster, from upgrading, using JSON for code reviews, to overall performance. Its a fun toy, leave it at that.
I'd be happy to take your experience into account in case I'll need to vouch this in the future. But unfortunately it's not very clear what shortcomings of Node-Red were a problem for you. Could you rephrase your experience, focusing on what you believe Node-Red does wrong?
N8n vs. node-red
31–40 of 69 posts
Re: N8n vs. node-red
#32What is an “antigenic AI” or “antigenic workflow” in this context? It’s used so consistently that I’m not sure if it’s just careless editing or if it’s something new I don’t know about.
Re: N8n vs. node-red
#33I understand nothing of this article. What does it mean by "n8n" lacks a UI? All it has is a UI, what use cases does the UI not handle? The writing is very poor and does not make sense at all.
Re: N8n vs. node-red
#34Re: N8n vs. node-red
#35I understand nothing of this article. What does it mean by "n8n" lacks a UI? All it has is a UI, what use cases does the UI not handle? The writing is very poor and does not make sense at all.
Re: N8n vs. node-red
#36I understand nothing of this article. What does it mean by "n8n" lacks a UI? All it has is a UI, what use cases does the UI not handle? The writing is very poor and does not make sense at all.
agreed, I'm running it on my localhost right now and it's got a full WYSIWYG interface. This article is slop
Re: N8n vs. node-red
#37It pains me to see all these “node” based automators charging you an arm and a leg. I can’t wait till people see the obvious and just replace them with a few prompts to Claude Code or similar.
What n8n gives is a nice gui. They’re going after the people who use Zapier, not the people who use Claude code
Re: N8n vs. node-red
#38Do these tools still make sense when you can have an agent-type setup like Claude Code or any of the competitors do that kind of low level work? I know that vibe coding isn't quite there yet, but I wonder if low-code solutions like those are really saving any time at this point. What's the advantage if not velocity?
But I think it depends on how many built in integrations there are? As if you have a battle tested integration already in place may save writing a script/api.
Also junior devs could be allocated on to it.
Re: N8n vs. node-red
#39https://github.com/activepieces/activepieces https://github.com/kestra-io/kestra
Re: N8n vs. node-red
#40I understand nothing of this article. What does it mean by "n8n" lacks a UI? All it has is a UI, what use cases does the UI not handle? The writing is very poor and does not make sense at all.
Sorry, I should have made myself clearer, I did not mean the UI that you use to create flows with, both systems are drag and drop flow creators. The issues I come across is visualizing what is going on inside of a system once it is created and up and running. I normally would like to have a dashboard showing me what is going on inside of a system. The node-red comes with Dashboard 2 ( a vue based set of components) for displaying whats going on in a live system. But I could not find a similar tool for n8n.
But then n8n has things I am missing from node-red, especially wrappers around LangGraph. I have to code those manually, in a node-red function node and it's not a simple task :(