PromptList w/ Template

Impact Pack's PromptList is a staple for batch prompting: type several prompts into one node, get a list out, run them one per iteration. This node is that idea with the one feature the original lacked - you can save the whole set as a named template and reload it later, instead of retyping your test batch every time you open a workflow. The display name says it: "PromptList w/ Template."

It's the "load five prompts into a list" node for people who keep rebuilding the same prompt grids.

How it works

Five multiline text fields (prompt_1 … prompt_5) get collected into a list, skipping any that are empty. An optional optional_prompt_list input prepends existing list content, so you can merge an upstream list (wildcard output, another template, whatever) with the five typed slots. The result goes out as both a LIST (for list consumers like ListSelector or batch loops) and a flat list of strings.

Templates are stored as JSON in the pack's santodan_nodes/prompt_list_templates folder - one file per template, viewable and deletable from the frontend buttons. The template_file dropdown lists every JSON in that folder plus "None," and save_filename is where you name a template you're about to write (with placeholder subfolder/template_name.json, so you can organize them in subfolders). When you select a template in the dropdown it loads its prompts into the five fields.

Inputs / outputs

• prompt_1 … prompt_5 - your prompt slots (multiline; empty ones are skipped).
• template_file - dropdown to load a saved template, or "None."
• save_filename - name to save the current five as.
• optional_prompt_list - a LIST to merge in ahead of the typed prompts.
• Outputs: prompt_list (a LIST) and prompt_strings (the same content as a list of strings).

Gotchas

• The template dropdown won't include templates until they exist. It's built by scanning the prompt_list_templates folder at load. Save a template and it should appear in the dropdown without a restart - if it doesn't show, refresh the frontend.
• The node packs example templates. The brief lists a few sample files (WildcardsExamples.json, modelTest.json, and friends) that ship in the folder - they're examples, not requirements. Delete them if they clutter the dropdown; the folder is just data.
• Empty slots are silently skipped. Five fields, but a list of two is fine. It also means you can't intentionally include a blank prompt in the list - if you need that, an upstream optional_prompt_list is the workaround.
• It's a list producer, not an iterator. Pair it with ListSelector (same pack) or Impact's loop machinery to actually walk the list one prompt per run.

Install

ComfyUI Manager (search "Santodan"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/Santodan/santodan-custom-nodes-comfyui

Restart. No dependencies, no downloads - templates are just JSON files in the pack folder.