Protoface Kling 3.0 Pro Shot

Search "Kling 3.0 Pro Shot" in ComfyUI's Add Node menu and you get two results with the same name, the same category, and near-identical fields. That's not a duplicate install. The pack mints one helper per list-item schema, and Kling 3.0 Pro's text-to-video and image-to-video operations publish slightly different ones - so you get two nodes, and each connects only to its own list.

This is the text-to-video one.

What it's for

Kling 3.0 Pro's multi_prompt control turns one generation into a storyboard of up to six shots. Set the control to Set and wire one Protoface Kling 3.0 Pro Shot helper per shot; the pack assembles them into an ordered list by the item_1, item_2, … socket numbering. multi_prompt is mutually exclusive with the model node's plain prompt - one continuous shot or a storyboard, not both.

The difference from its twin is subtle but real. Here prompt is optional: it sits in Default/Set mode, and on Default it's simply omitted from the request. The image-to-video variant requires a prompt on every shot. So if you're working from a reference image and want a beat to be "whatever the model does with this frame," this is the helper that lets you say nothing.

The two fields

prompt (optional, Set-mode): the shot's description. Set it and it goes to the API; leave it on Default and the shot carries only its duration, letting the model fill in. That's genuinely useful when you've supplied an image elsewhere in the graph and want the model to choose the motion, and it's less useful when you actually have a shot in mind - a silent beat is a lost instruction, not a clever one.

duration is a COMBO of integers 3 through 15, default 5. The floor is 3 seconds here; Kling 3 Turbo's helper is the one that goes down to 1.

The output, value_out, is typed PROTOFACE_VALUE_b2dd1a3a8193c750. That's a digest of this exact item schema, which is the whole explanation for the twin-node situation: different schema, different type, different node. It will connect to Kling 3.0 Pro's text-to-video multi_prompt and refuse everywhere else.

Why the name doesn't help you

The pack derives display names from the model and the control, not from the operation, so both Kling 3.0 Pro helpers are labelled identically. The socket type is the only reliable discriminator in the menu, and you can't read socket types without connecting. Practical approach: connect, and if it doesn't fit, try the other one. ComfyUI refuses the link, nothing breaks, no credits move.

Worth saying out loud because it looks like a bug and isn't: the pack's own model nodes carry an immutable schema identity, and their helper nodes follow it. When a provider revises a schema, a new helper ID appears rather than the old node silently changing meaning under your saved workflow. The cost of that safety is duplicate-looking entries in the menu.

Inputs and outputs, plainly

prompt (STRING, optional / Default-Set): this shot's description.
duration (INT combo, 3–15): this shot's length.
value_out (typed PROTOFACE_VALUE_b2dd1a3a8193c750): into the Kling 3.0 Pro text-to-video node's multi_prompt.

Value carrier only - no API call, no key, no charge.

The arithmetic nobody validates for you

Kling 3 Turbo's shot list has a hard rule that shot durations must sum to the clip's total duration, enforced by the pack before submission. Kling 3.0 Pro's text-to-video contract, as published in this pack's catalog, has no such rule - so shot durations that don't add up aren't caught locally. Set the model node's duration first, then split it. At roughly 32 credits per output second, a lopsided storyboard is an expensive way to learn that.

Install

cd ComfyUI/custom_nodes
git clone --branch v0.1.0 --depth 1 https://github.com/protoface-ai/protoface-comfyui.git protoface
python -m pip install -r protoface/requirements.txt

or Manager → Protoface → protoface-nodes → restart → reload the browser. ComfyUI 0.41.0+, Python 3.10+, requirements installed with ComfyUI's interpreter. The model node downstream needs a key from the Protoface panel in the lower right; servers can use PROTOFACE_API_KEY or PROTOFACE_API_KEY_FILE instead, which survives restarts.