The Kling O3: FLF2V workflow is designed to generate videos with precise semantic control and enhanced narrative coherence. This workflow leverages the Kling O3 model, which is known for its ability to maintain consistency across frames while allowing for detailed control over the video’s storyline. By using nodes such as SaveVideo, LoadImage, and BatchImagesNode, users can upload reference images to guide the video's context or specify start and end frames for a structured narrative. The KlingOmniProFirstLastFrameNode is particularly crucial as it facilitates the seamless transition between frames, ensuring that the narrative flow remains uninterrupted. This makes the workflow especially useful for creating longer-duration videos where maintaining thematic consistency is essential.
API
Use this workflow from code
Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.
Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.
// Install (beta)
npm i @comfyorg/sdk
// Run "Kling O3: FLF2V" (TypeScript)
import { Comfy } from "@comfyorg/sdk";
const client = new Comfy({ apiKey: "comfyui-..." });
// This workflow, exported in API format (see note below)
const wf = await client.workflows.fromFile("api_kling_o3_flf2v_api.json");
const asset = client.assets.fromFile("input.png");
wf.setInput("36", "image", asset); // LoadImage
const job = await client.run(wf);
await job.getOutputs("14")[0].toFile("output.png"); // SaveVideoThe SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).
Comfy Cloud API access requires a plan with an API key.
FAQ
