Protoface Kling 3.0 Pro Shot

Kling 3.0 Pro will storyboard a multi-shot video for you: instead of one prompt describing a whole clip, you declare up to six shots, each with its own words and its own length, and the model cuts between them. Each of those shots is a node. This one - Protoface Kling 3.0 Pro Shot - holds a prompt and a duration, and it's the variant that pairs with Kling 3.0 Pro's image-to-video operation.

What it's for

On the Kling 3.0 Pro model node in this pack, the multi_prompt control is a list. Set it to Set and connect one helper per shot. The helpers are generated from the model's request schema, and each gets a socket type derived from that item schema - here PROTOFACE_VALUE_8e552c848068adfd. That digest is why this node will slot into Kling 3.0 Pro's shot list and nowhere else.

multi_prompt is mutually exclusive with the node's plain prompt widget: you're either describing one continuous shot, or writing a storyboard. Both at once is a validation error, not a creative choice.

The two fields

prompt is a multiline STRING and it's required here, minimum one character. This is the difference between the Kling 3.0 Pro helpers that matters in practice: in this schema each shot must say something. There's no "inherit the global prompt" behaviour at the shot level, so a silent beat means writing "static wide shot, no action" rather than leaving the box empty.

Keep each shot short and specific. One camera idea and one subject action per shot is what a multi-shot model can actually honour; a paragraph per beat tends to get averaged into mush across the cuts.

duration is a COMBO of integers from 3 to 15, default 5. Note where it starts: 3 seconds, not 1. If you're cutting a fast storyboard, the Turbo variant of this helper goes down to a single second and this one doesn't.

Inputs and outputs, plainly

• prompt (STRING, required): this shot's description.
• duration (INT combo, 3–15): this shot's length.
• value_out (typed PROTOFACE_VALUE_8e552c848068adfd): into Kling 3.0 Pro's multi_prompt list.

No API call, no key, no cost - it's a value carrier. The list control itself caps at six items, and the pack grows item_1, item_2, … sockets as you connect, adding them in numeric order.

One thing the Turbo helper does that this one doesn't

Kling 3 Turbo's multi-shot contract carries an explicit rule that the shot durations must sum to the node's total duration, and the pack validates it before submitting. Kling 3.0 Pro's contract, in this pack's catalog, has no such rule attached - so nothing stops you from wiring four shots of 10 into a 5-second clip. Whether the API trims, ignores, or errors is between you and the provider.

Which means: do the arithmetic yourself. Set the model node's duration first, then distribute it across your shots, and keep the sum equal. On a per-second meter around 32 credits, that discipline is worth more than it sounds.

Also worth knowing on the Pro node, since it changes how shots are interpreted: shot_type is customize or intelligent, defaulting to customize. customize is the mode where your per-shot prompts actually drive the cut.

Install

Ships with the pack:

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 → search Protoface → install protoface-nodes → restart → reload the browser. ComfyUI 0.41.0+, Python 3.10+, pip run with ComfyUI's interpreter so httpx, jsonschema, Pillow and av land in the right environment. The Kling node downstream needs a key from the Protoface panel in the lower right, or PROTOFACE_API_KEY / PROTOFACE_API_KEY_FILE on a server.

Where people get stuck

Two nodes, same name. Add Node search shows this and another helper both called "Protoface Kling 3.0 Pro Shot". They differ: this one is the image-to-video contract, the other is text-to-video, and only one of them will connect to your particular model node. The socket type is the tell.

Sum drift. Nothing validates the total for Kling 3.0 Pro, so a mismatch surfaces as a provider-side surprise rather than a red node.

Key in memory. Restart ComfyUI and every Protoface node needs the key re-entered. That's not a broken install.