The 'Kling 3.0: Motion Control' workflow is designed to seamlessly integrate character images with motion reference videos to generate new, dynamic video content. By utilizing the Kling 3.0 model, this workflow allows users to upload a static character image and a motion reference video, and then it synthesizes a new video where the character mimics the actions from the reference. The process is enhanced by the KlingMotionControl node, which ensures that the character's facial features remain consistent throughout the video, even as it performs complex movements. This is particularly useful for applications requiring high fidelity in facial expressions and movements, such as animation and game development. The workflow also includes optional element binding, which can be used to further refine the character's interaction with the environment or other elements in the video.
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 3.0: Motion Control" (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_motion_control3_api.json");
const asset = client.assets.fromFile("input.png");
wf.setInput("2", "image", asset); // LoadImage
const job = await client.run(wf);
await job.getOutputs("4")[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
