Griptape Create: Text
The Node That Just Holds a String
- OUTPUT
Griptape Create: Text is the pack's plainest node: a multiline text box that outputs exactly what you type. No LLM, no processing, no surprises. You type a string, you get that string back on the OUTPUT wire. It's the "here's some text, do something with it" starting point for Griptape workflows - the equivalent of ComfyUI's built-in text input nodes, but shaped to drop cleanly into this pack's STRING inputs.
What it's for
Griptape nodes are picky about where text comes from - many expect a STRING wire rather than letting you type directly into a prompt field (some inputs are marked forceInput, meaning they can only be filled by a connection). Create Text is how you get text into those. It also gives you a convenient staging point: type a prompt here, wire it to an agent or task, and you can swap the text without digging into the node's internals.
It's also a good debugging stop - because it's an output node, whatever you put in shows up clearly, and you can use it as a junction to split a string to multiple destinations.
How it works
Straight passthrough:
def run(self, STRING):
return (STRING,)
The only meaningful behavior is that it's an output node, so its value is displayed when the workflow runs - which makes it useful as a way to see a string at a point in the graph, even if that string came from somewhere else.
Inputs and output
STRING(STRING, multiline) - the text. Type it, or leave it empty and it outputs an empty string.- Output:
OUTPUT(STRING) - the same text, ready to wire into agent prompts, task nodes, or other STRING inputs.
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.
No dependencies beyond the pack itself. This node makes zero network calls.
Gotchas
- It does nothing to your text - no trimming, no escaping, no dynamic prompt processing. If you expect
{{ key }}replacement here, it won't happen; that's handled by the agent/task node downstream viakey_value_replacement. - Because it's an output node, connecting it in the middle of a workflow means ComfyUI displays its value every run. Harmless, but it does mark the node as a terminal in the graph.
The most useful boring node in the pack. Every workflow needs a text source, and this is the one that never surprises you.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| STRINGopt | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| OUTPUT | STRING | — |