EchartGraph_clh

This is the display end of the pack's little charting trio. It takes an ECharts options string - the JSON config that describes a chart - and renders the actual chart right on the node. The two EchartOption nodes build that config; this one draws it. On its own it does nothing useful, which is the first thing to understand about it.

Charting inside ComfyUI is a genuinely niche thing to want. But if your workflow is churning out numbers - a batch of scores, a settings sweep, tallied results from a JavaScript clh node - being able to eyeball them as a bar or line chart without leaving the graph is the payoff. This node is what makes the picture appear.

How it works

ECharts is config-driven: hand it one options object and it knows how to render the whole chart. EchartGraph clh is essentially the render surface for that object. You feed the options string into it, and it displays the resulting chart on the node face - it's an output node, so it forces execution and shows you the result even with nothing wired downstream. There are no output sockets; the chart is the output. It's a terminal, look-at-it node, not something you pipe onward.

The inputs and outputs that matter

There's really just one input:

• chartOptions - the ECharts options string. In practice you don't type this by hand; you wire it in from the options output of EchartOption clh (plain arrays) or EchartOptionByPath clh (pull values out of a JSON blob by path). The default in the box is a placeholder - replace it with a real config or, better, connect one of the option-builder nodes.

No outputs. The node renders and stops. That's the design.

The three-node pipeline

Worth spelling out because none of these nodes is useful alone:

1. EchartOption clh or EchartOptionByPath clh - builds the options config from your data.
2. Wire that options output into this node's chartOptions input.
3. EchartGraph clh - renders it.

Get that chain right and you have a chart. Miss the first step and you have an empty node wondering what you want from it.

Installing it

ComfyUI Manager: search Clh Tool for ComfyUI, install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/clhui/ComfyUi-clh-Tool

then restart ComfyUI. After a manual clone, check the startup console - a Manager install pulls a pack's dependencies for you, but a bare git clone leaves you to pip install anything it reports missing. A rendering-heavy node like this is exactly the kind that leans on a library, so if it loads but shows nothing, the console log is the first place to look.

Common issues

Blank node? Almost always the chartOptions string is empty, malformed, or you never connected an option-builder to it. Confirm the upstream EchartOption node is actually producing a valid config first - if that's broken (bad arrays, a wrong path expression), this node has nothing to draw. Debug backwards: fix the options, and the chart follows.

Nothing rendered but no error? Because this node depends on a charting library doing the actual drawing, a silently-missing dependency can leave you with a node that runs but paints nothing. The ComfyUI console at startup is where a missing import shows up.

And keep the mental model straight: this node never touches your data or your images. It's a viewer. All the shaping - which values, which chart type, which labels - happens in the option node upstream. If the chart's wrong, that's where you go to fix it.