Nodes/ComfyUI-YogurtNodes/Save Text Bridge (Non Output) (Yogurt Nodes)
ComfyUI Node

Save Text Bridge (Non Output) (Yogurt Nodes)

The text logger that never shows up in results

By yogurt7771·Created 2 years ago·Updated 9 days ago· 1
Save Text Bridge (Non Output) (Yogurt Nodes)
    • text
    • path
    content
    output_dir
    filename_prefixComfyUI
    overwritefalse
    suffix.txt
    custom_suffix

    Save Text Bridge (Non Output) is the logging node: it writes text to a file, passes the text back through the graph, and doesn't register itself as a workflow output. If "save this for later" is the whole job, this is the version you want.

    The behavior is identical to the regular Save Text Bridge - same inputs, same text and path outputs, same file-writing mechanics. content in, choose output_dir (blank → ComfyUI output), filename_prefix (with %date:yyyy-MM-dd% tokens), suffix (.txt, .json, .md, .csv, or Custom with a custom_suffix), and overwrite (off by default). The one difference is is_output_node being false, and that difference is the reason this variant exists.

    Here's what "not an output node" buys you for text specifically. ComfyUI returns output nodes' results in the API response and surfaces them in the frontend. When you're driving ComfyUI programmatically - and especially with this pack's own ComfyUI Client nodes, which run one instance from another - a chat log or a prompt record suddenly appearing as a "workflow output" is pure noise. Non-output keeps the artifact on disk without polluting your results. If this node lives in a subworkflow, it also means the log doesn't bubble up to the parent graph as a deliverable.

    The honest workflow use

    Prompt logging is the killer app. Assemble a prompt (or have an LLM node produce one), tee a copy into a .md or .csv log file, and let the text keep flowing to the encoder. The path output tells you exactly where the log landed, which plays nicely with the pack's path utilities if you want to track it programmatically.

    Install

    All Yogurt nodes come from the one pack:

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

    or ComfyUI Manager → ComfyUI-YogurtNodes → install → restart. Under Yogurt Nodes → IO.

    Gotchas

    Same as the output-marked version: the extension is cosmetic - .json doesn't validate or format your content, so stringify real objects upstream (YogurtJsonStringify does that). And "non output" means no gallery entry: check the folder or the path output to confirm the write. One more for the loggers: overwrite=false stacks numbered files, which is usually what you want for logs; flip it on only if a fixed path matters.

    CategoryYogurtNodes/IO

    Inputs (6)

    NameTypeDefaultDescription
    contentSTRINGThe text to save.
    output_dirSTRINGThe directory to save the text to, leave blank to save to the ComfyUI output directory.
    filename_prefixSTRINGComfyUIThe prefix for the file to save. This may include formatting information such as %date:yyyy-MM-dd%.
    overwriteCOMBOfalseOverwrite existing files.
    suffixCOMBO.txtThe file extension to save the text as.
    custom_suffixSTRINGThe file extension to save the text as. If this is not empty, the suffix option will be ignored. Otherwise, the suffix option will override above suffix option.

    Outputs (2)

    NameTypeDescription
    textSTRING
    pathSTRING