Tag Data Loader (Danbooru)

This node does one thing: it hands you back a collection of Danbooru tag data you saved earlier, by name, instead of you re-running the search that produced it. It's the "load" half of a save-then-reuse workflow, and on its own it looks almost too simple to need explaining - one dropdown, one output - but that simplicity is the point. It's not meant to stand alone; it's meant to plug into the Danbooru source node so you can pull the same well-tagged prompt collection over and over without touching the network again.

Why you'd reach for it

Say you found a Danbooru query that returns exactly the character and style tags you want - good hit rate, clean results. Re-running that query every session works, but it also means another API round-trip every time, and you're at the mercy of whatever images happen to match right now. Save that pull once with Tag Data Saver, and from then on the Loader gets you back to that exact same tag pool instantly, offline, with zero API calls. It's the difference between re-searching a library every visit and just pulling the book off your own shelf.

The inputs and outputs that matter

There's exactly one field: collection_name, an enum dropdown listing your saved Danbooru collections. If you haven't saved anything yet with the Saver node, this dropdown is empty - that's expected, not a bug. It populates as soon as you save at least one collection under a name.

The output, tag data, is typed LPP_TAG_DATA_DANBOORU - the booru-specific type, not the generic one. That distinction matters: this is the exact type the Danbooru source node's optional tag_data input expects. Wire this Loader's output there, leave send_request off on the source node, and it works from your saved collection instead of querying Danbooru fresh. Pair it with the source node's format and prompt_template fields to re-format or re-roll a different random prompt from the same underlying tag pool without ever hitting the API again.

How to install it

It ships as part of the Lazy Pony Prompter pack, so there's no separate install - get the pack once and every LPP node, including this one, is available. Via ComfyUI Manager, search "Lazy Pony Prompter" and install. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Siberpone/lazy-pony-prompter

Restart ComfyUI either way. No model downloads, no extra dependencies to chase down. All LPP nodes live under the LPP group in the node menu, so once it's installed you'll find this one under LPP/loaders.

Common issues & troubleshooting

The dropdown is empty. This is the single most common point of confusion with the loader nodes, and it's not a bug - you haven't saved any Danbooru collections yet. Run the Danbooru source node with send_request on, wire its LPP Tag Data output into Tag Data Saver, give it a name, and the dropdown will populate on the next check.

Loaded data doesn't match what you remember saving. Collection names aren't automatically unique across sessions - if you or a previous save reused a name, the Saver's overwrite flag decides whether it got clobbered. If a collection looks wrong, check whether something overwrote it.

Wiring it into the wrong input. This node's output type is booru-specific (LPP_TAG_DATA_DANBOORU), so it'll only connect to inputs expecting that exact type - the Danbooru source node's tag_data input, specifically. It won't wire into the E621 or Derpibooru source nodes, and it's a different type than what Tag Data Saver itself expects on its input (that one takes the generic LPP_TAG_DATA, the type the source nodes output alongside their Prompt). If a connection refuses to snap, that type mismatch is almost always why.

General rough edges. The pack's ComfyUI nodes are described by the author as "somewhat experimental" with some ComfyUI-specific UX compromises. If something behaves a little oddly, that's a known, acknowledged limitation of the ComfyUI port rather than something you configured wrong.