Auto Prompt Schedule

Auto Prompt Schedule doesn't generate anything. No model, no API, no key. It's a tiny string utility with a very specific job: turn a plain list of prompts into the keyframe format that FizzNodes' Prompt Schedule node eats. That sounds unimpressive until you've tried to batch 20 prompts through a workflow and had to type "0":"...", "1":"...", by hand. That's the whole problem this kills.

The catch, and it's in the README first thing: this node is useless on its own. It's a helper for FizzNodes (ComfyUI_FizzNodes), so you need that pack installed too - the Prompt Schedule node is the actual consumer. Think of Auto Prompt Schedule as the front-end for the schedule text box you'd otherwise fill manually.

How it works

The mechanism is trivial and it's all in the name. Every non-empty line of text becomes a keyframe: line 0 lands at frame 0, line 1 at frame 1, and so on. The output is a schedule string in FizzNodes' format - a "frame":"prompt", pair per line - which you wire straight into the Prompt Schedule node's text input. A second output, info_text, just prints "Number of lines: N / Number of runs: M" so you know how many queue runs your batch needs. It's a debug readout; wire it into ShowText if you want it visible.

One thing to know before you get excited about animation: prompts don't blend. The author's own workflow note is explicit - each prompt stays active until the next keyframe is reached, then it hard-swaps. So this node is for discrete prompt-to-image batches (one image per line), not smooth text interpolation. FizzNodes has separate machinery for gradual prompt drifting; this isn't it.

The inputs that matter

Three inputs, all in required, none of them scary:

• text - multiline. Each line is one prompt. One line per prompt, empty lines are skipped.
• file_path - optional absolute path to a .txt file. If it's filled, it overrides text. Handy when your prompt list lives in a text file next to the workflow.
• multiplier - default 1, minimum 1. Spacing between keyframes. Multiplier 3 gives you keyframes at 0, 3, 6, 9… instead of 0, 1, 2, 3. Only reaches for this if your downstream workflow is keyed to non-consecutive frames.

Installation

The pack itself has zero dependencies - no requirements.txt, pure Python standard library, so nothing to fight over in your shared environment. Install via ComfyUI Manager (search "Auto Prompt Schedule") or:

cd ComfyUI/custom_nodes
git clone https://github.com/ReinerBforartists/comfyui_auto_prompt_schedule

Restart ComfyUI. The node shows up under Text as "Auto Prompt Schedule". Don't forget the FizzNodes install - it won't appear here, but without it you've got nothing to feed the output into. The pack ships an example workflow (Flux dev fp8 based) that shows the whole batch setup, including a separate style prompt appended via FizzNodes' app_text so you don't paste the style into every line.

Gotchas that will bite you

• Reset the frame counter to 0 before a fresh batch. The example workflow drives the Prompt Schedule node's current_frame from a PrimitiveInt that auto-increments per run. If you rerun a batch without resetting it, you start mid-schedule. The workflow has an "IMPORTANT" note screaming exactly this.
• Absolute paths only for file_path - relative paths won't resolve the way you hope.
• Trailing commas in the schedule are normal. Every generated line ends with , including the last one; FizzNodes parses it fine. Don't "fix" it.

From the Bforartists side of the Blender world, the author ships workflows with real care - the included example is properly documented with notes, not just dumped. For a one-job utility that's more than most packs manage. The node is new (v1.0, mid-2025) and lightly used, but it's hard to break something that's just string formatting.