Hacker News new | ask | show | jobs
by guhcampos 332 days ago
I 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.

4 comments

Thanks for reading my article.

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 :(

Well not “all” it also has the permanently running workflow engine bit that actually runs the workflows in the background. But yeah same here, very confused about the write up.
n8n doesn't have a customer facing ui.

It's a question that comes up often from low/no-code creators.

agreed, I'm running it on my localhost right now and it's got a full WYSIWYG interface. This article is slop
thank you for your kind words, I obviously was not clear in how I wrote the article, AI might have picked it up. But I am old school and type everything my self. It's part of the feynman learning process I use.

However I have updated the article so it is much clearer, the UI that is missing from n8n is not WISIWIG, but a management dashboard, to be viewed once the system is live. I have added the following:

"To be clear here, 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."

How did they write their workflows then, in json?