Checkbin Save String Bin

What it's for

Checkbin Save String Bin is the text counterpart to Save Image Bin. Where its sibling uploads an image as a candidate in a Checkbin comparison, this one records a string - a prompt, a caption, a style label, a setting summary - under a name. If your A/B test is "which prompt produces a better render" or "which caption is more accurate," you don't always need to ship pixels; sometimes the voters should see the text that drove the generation.

It's the smallest node in the pack, and that's fine. It exists to let a Checkbin run carry metadata alongside images so the voting page has context for what's being compared.

How it works

Straight from bin_node.py: it takes a bin, a string, and a name, calls bin.checkin(name) to reserve the slot, then bin.add_state(name, string) to attach the text to it. Same pattern as the image version, just a string instead of a tensor upload. And like its sibling, it's a pass-through - it returns the same bin and the same string it received, so you can keep the flow going without losing the value.

There's no local file involved and no conversion step. The string goes over the wire to Checkbin's servers verbatim, tagged with whatever name you chose.

The inputs that matter

All three are required:

• bin - the CHECKBIN output from Start Run or an upstream save node.
• name - the slot label. Keep it unique within the bin and identical to any Get String Bin name you plan to use downstream.
• string - the actual text to store. Wire it from your prompt builder, captioner, or any node that emits a string.

The outputs

bin and string, both pass-throughs. If you're saving a string that you still need downstream (say, the same prompt feeds a CLIP Text Encode), keep the string output connected.

Installing it

Same pack as the other five Checkbin nodes - install checkbin-comfy once and you're done:

cd ComfyUI/custom_nodes
git clone https://github.com/checkbins/checkbin-comfy

Restart ComfyUI afterwards, or grab it through ComfyUI Manager by searching "checkbin-comfy". Its only dependency is the checkbin Python package; there are no model downloads and no GPU footprint. Everything this node does is an HTTP call to Checkbin's service.

Common issues

• Non-string data gets rejected - the node refuses to save anything that isn't a str (the source raises a Data is not a string error). If your upstream node emits an int, a float, or a JSON object, stringify it first.
• Duplicate names collide - like the image node, reusing a name within a bin overwrites or conflicts with the earlier checkin. Pick distinct labels per candidate.
• Name drift - save under one spelling and fetch under another and you'll hit the No data found with name error on the Get side. Names are plain strings; copy them, don't retype them.