Griptape Display: Data as Text

Griptape Display: Data as Text is the "show me what's actually in this wire" node. It accepts almost any input - text, dictionaries, agent outputs, whatever - stringifies it, and displays it in the ComfyUI UI so you can see it. The input type is *, the wildcard, which means it accepts basically anything the graph throws at it. That's the entire point: a universal eyeball for debugging.

What it's for

Griptape workflows pass around a lot of invisible state - agent replies, dictionaries of key-value replacements, module outputs. When something isn't working, the first question is always "what did that node actually produce?" This node answers it. Wire the suspicious output in, run the workflow, and the UI shows you the stringified value. It's the difference between guessing and knowing.

It's also the node you reach for when you want to persist a value in a visible way or split a value into a display branch while the real branch continues on - because it's an output node, it doesn't interrupt anything.

How it works

The func is a stringification + display:

return {"ui": {"INPUT": str(INPUT)}, "result": (str(INPUT),)}

Whatever comes in gets str()'d and pushed to the UI. Dictionaries become their repr, numbers become text, agent output stays as-is. The same string also flows out the OUTPUT wire, so you can chain it or feed the display result onward - though realistically you're using it as a terminal.

Inputs and output

• INPUT (*, multiline, force-input) - anything you want to inspect. Connect it; you generally can't just type here.
• Output: OUTPUT (*) - the stringified value, passed through.

Installation

Part of ComfyUI Griptape Nodes:

• ComfyUI Manager: search "Griptape" → install.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/griptape-ai/ComfyUI-Griptape, restart ComfyUI.

Gotchas

• The output is a string even though it's typed *. If you wire it into something expecting structured data, you'll get the text repr of it, not the data.
• Empty input → empty display. If the node shows nothing, check whether the upstream node actually produced a value before you suspect the display node.
• It's for inspection, not transformation. It doesn't pretty-print, format, or parse - you get the raw str(). For dictionaries that reads like {'key': 'value'}.

Every debugging session in this pack starts with one of these. When in doubt, wire it in.