flow_createbatch

This is about as small as a utility node gets: two wildcard-typed inputs in, one combined batch out. No description ships with it, but the shape is self-explanatory - it's the pack's basic building block for assembling a batch or list out of individual values, one pair at a time.

How it works

Wire anything into any_1 and any_2 - images, latents, strings, whatever type they happen to be, since both sockets accept * - and the node hands back a single batch output combining them. It's filed under Apt_Preset/stack/register, which puts it alongside the pack's batch-loading tooling (the README's changelog mentions IO_LoadImgBatch, IO_LoadTextBatch, and IO_LoadShotBatch as related, more recent additions) rather than the general-purpose flow category most of this pack's control nodes live in - so think of it as a batch-registration primitive more than a generic flow-control node.

Because the output is itself the same wildcard * type as the inputs, it's reasonable to assume you can chain flow_createbatch nodes - feed one instance's batch output back in as any_1 or any_2 of a second instance to build up a bigger batch two items at a time. The schema doesn't confirm that chaining is supported, though, so treat it as a plausible pattern to try rather than a documented one.

Inputs and output

• any_1, any_2 (required, wildcard) - the two values to combine.
• batch (output, wildcard) - the combined result.

Installing it

Search ComfyUI-Apt_Preset in ComfyUI Manager and install, or manually: cd ComfyUI/custom_nodes && git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git, then restart. The README's dependency step is "double-click install.bat" - Windows-first phrasing, with no requirements.txt visible elsewhere, so on Linux/Mac open that file to see what it installs and mirror it by hand in your ComfyUI venv. This node is pure data plumbing and needs none of the pack's optional extras (GGUF, Advanced-ControlNet, nunchaku, downloaded models).

Common issues

Since both inputs and the output are wildcard-typed, ComfyUI won't stop you from combining two things of different types - an image and a string, for instance - into one "batch." If a downstream node then errors in a confusing way, check that both of your inputs are actually the same underlying type before assuming the node itself is broken.

If you're trying to chain multiple flow_createbatch nodes to build a larger batch, verify the result actually grows the way you expect on a small test first - the pack doesn't document this pattern explicitly, so don't assume it until you've seen it work.

And the pack-wide caveat: this is one node inside a large, actively developed package, and an import error anywhere in it can take the whole thing - including this node - offline. If it's missing after install, check the ComfyUI console at boot for the actual traceback rather than re-running your install steps blind.