📎CrewAI Text

This is the unglamorous but genuinely useful tail of the ComfyUI-CrewAI pack. When your 📎CrewAI Crew node hands you a positive and negative prompt pair, you have two options: wire them straight into CLIPTextEncode and let the image decide, or actually read them first. This node is the "read them first" option. It catches incoming text, shows it on the node so you can eyeball it, and optionally writes it to disk as a .txt file.

It's notable that this node doesn't live in the 📎CrewAI category - its category is Custom Nodes, because despite the name it's a generic text tool. The Crew node just happens to be its most common upstream.

The inputs

• text (required, forced input) - the string to display and save. This is where the Crew's positive/negative outputs plug in.
• output (multiline) - the on-node display widget. After the run, the pack's JS extension finds this widget and writes the incoming text into it, so you see the result right on the node. You can also type into it yourself; it's a display surface more than a control.
• filename_prefix (default output) - the base name for the saved file.
• save_file (enabled/disabled, default enabled) - whether to write the .txt file at all.
• save_metadata (enabled/disabled, default enabled) - whether to also write a small .json next to the file with timestamp, prefix, and a text preview.

Output: the same text as a STRING, so you can chain it onward.

Where the files go

A detail that catches people: it writes to outputs/text_outputs/ relative to your ComfyUI working directory - not your custom_nodes folder, not the input folder. So after a run you'll find:

ComfyUI/outputs/text_outputs/output_20260813_093045.txt
ComfyUI/outputs/text_outputs/output_20260813_093045_metadata.json

The timestamped filename means repeated runs don't clobber each other, which is handy for A/B testing topics against the same crew.

The typical use

Stick one after each of the Crew node's outputs, run the crew, read what your agents actually produced before you burn a diffusion pass on it. The pack's example workflows do exactly this - two Text nodes catching positive and negative, so you can hand-edit a promising prompt before it hits the sampler. If you'd rather skip the file clutter, flip save_file to disabled and keep it as a pure display node.

Installing

Ships with ComfyUI-CrewAI. ComfyUI Manager → search "ComfyUI-CrewAI", or:

cd ComfyUI/custom_nodes
git clone https://github.com/luandev/ComfyUI-CrewAI
cd ComfyUI-CrewAI
pip install -r requirements.txt

Restart ComfyUI. No models, no keys - it's a file/display helper, and one of the only nodes in this pack you can use even without an LLM backend wired up.