Prompt Store Headings (CCN)

This is the smallest node in the prompt-store family and probably the least interesting on its own - five text boxes and one output. Its entire job is to supply the section names for a Prompt Store Custom node. Wire its headings output into the Custom store's headings input, and your five sections stop being anonymous section_1…section_5 and become whatever you typed.

That's it. That's the whole node. It exists because ComfyUI has no native way to type a variable-length list of strings into a node and hand it off as a single value - so the pack ships a tiny one-purpose node that produces a CCN_PROMPT_HEADINGS blob.

How to use it

Fill in heading_1 through heading_5 with the names you want - "subject", "lighting", "composition", "camera", "vibe", whatever - and connect the output to a Prompt Store Custom. Leave a field empty and that section falls back to the generic section_N name on the store node. Store keys are derived by lowercasing your headings, so if you later fetch a category with Prompt Store Get, the case-insensitive lookup will match.

One nice property: because the headings travel as a wire, you can keep multiple sets of headings around in one workflow and swap which one feeds the store - a cheap way to A/B the same content under different category structures.

Install

Part of ComfyCollectorNodes, one install covers it:

cd ComfyUI/custom_nodes
git clone https://github.com/valkymaera/ComfyCollectorNodes

then restart ComfyUI, or install via ComfyUI Manager ("ComfyCollectorNodes"). No models, no extra dependencies.

Where people get burned

Honestly, not much to trip over here - it's five strings and a wire. The one trap: renaming a heading after a Custom store has already stored values under the old name. The store keeps the old keys; your new heading just starts a new slot, so data you thought was "renamed" is actually orphaned in the old key. If you rename, either clear the store first or expect to re-enter the section text. And if your headings don't seem to take effect, double-check that the wire actually connects the Headings output to the Custom store's headings input - an unwired input silently falls back to generic names.