Do I need an API key to use this workflow?

Yes. KlingOmniProTextToVideoNode calls the external Kling O1 service, which typically requires an API key and endpoint. Configure credentials in the node’s settings or environment as documented by the node.

What resolutions and durations are supported?

Limits depend on the Kling O1 service and the node’s implementation. Use the options exposed by KlingOmniProTextToVideoNode and stay within the recommended ranges shown in the node’s UI or documentation to avoid errors or long queue times.

How can I get smoother motion and fewer artifacts?

Write precise prompts with clear subject focus and camera instructions (e.g., slow pan, tripod shot). Keep clip lengths modest, avoid overly complex multi-subject actions in a single prompt, and choose a frame rate that matches the motion you want. Iterate with small changes and, if available, control the seed.

What format does SaveVideo output?

SaveVideo writes the clip to a file using the path and fps you set in the node. The exact container/codec options depend on your ComfyUI setup and the node’s parameters; MP4 is commonly used when available.

Kling O1: Text to Video - ComfyUI Workflow

This ComfyUI workflow turns plain-language prompts into short videos using the Kling O1 model. At its core is the KlingOmniProTextToVideoNode, which sends your prompt to the Kling service and receives a generated clip. The node handles prompt text and generation options (such as clip length and size), then passes the resulting video to SaveVideo, which writes the output to disk.

Technically, the KlingOmniProTextToVideoNode is the generation engine: it packages your prompt and settings, calls the Kling O1 API, and outputs a video stream or frame sequence as a single node result. The SaveVideo node consumes that output and saves it to a file, where you can control basics like output path and frame rate. For best results, write prompts that clearly define the subject, action, setting, and camera behavior (for example: "wide shot, slow dolly-in, golden-hour lighting"). Keep durations and resolutions within the node’s supported ranges to reduce errors and queue times. If the node exposes a seed, fix it to make variations more reproducible.

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.

GET https://comfy.org/workflows/download/9654558acd06.json

Fetching workflow JSON…

Run it from Python or TypeScript with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

# Install (beta)
pip install comfy-sdk        # Python
npm i @comfyorg/sdk          # TypeScript

# Run "Kling O1: Text to Video" (Python)
from comfy_sdk import Comfy

client = Comfy(api_key="comfyui-...")

# This workflow, exported in API format (see note below)
wf = client.workflows.from_file("api_kling_omni_t2v_api.json")

job = client.run(wf)
for output in job.get_outputs("16"):  # SaveVideo
    output.to_file(output.name)

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API). API access requires a Comfy Cloud plan with an API key. SDK docs · Get an API key

FAQ

Frequently Asked Questions

View all workflows