KIE Grok Imagine (I2V)

Grok Imagine's image-to-video node is where the pack's Grok chain pays off. You've got two ways in: drop in an external image directly, or - the more interesting path - pass a task_id from the pack's Grok T2I or I2I node plus an index, and Grok animates one of the images it already generated server-side. No downloading your result to disk, no re-uploading it as a video source. The whole thing stays inside the API, which is both faster and cheaper.

That task_id path is genuinely unusual and worth understanding, because it's the reason the Grok image nodes bother returning a task_id at all. This node is the other end of that wire.

How it works

Standard KIE video job lifecycle (createTask → poll recordInfo, 2000-second timeout, auto-retry on transient failures). The subtle part is the source resolution: the node takes exactly one source method - either images (external, single image) or task_id (a Grok generation reference). The pack validates that for you. If both are set, it refuses; if neither, it refuses.

The inputs that matter

• prompt - optional text (up to 5000 chars) describing the motion you want.
• images - one external source image, if you're going that route. External mode supports only a single image.
• task_id - the Grok task reference from a T2I/I2I node. This is the chain input.
• index - 0–5, default 0. When using a task_id, this picks which generated image in the batch animates. The pack's image nodes can return multiple images, so this is how you choose.
• mode - fun, normal (default), or spicy. Here's the catch: spicy mode only works with task_id sources. If you want the permissive content mode, you have to go through a Grok generation first.
• duration - 6, 10, or 15 seconds (default 6). resolution - 480p (default) or 720p.

Output: video, ready for preview or a saver.

Installing

Part of the pack, installed once. ComfyUI Manager: search "ComfyUI Kie API". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/gateway/ComfyUI-Kie-API
# restart ComfyUI

No model files. API key at config/kie_key.txt in the pack folder (copy from kie_key.example.txt).

Where people get burned

The source-method rule is the #1 trap: connect both an image and a task_id and the node errors out - pick one deliberately. If you set index but fed an external image, the index does nothing; it only applies to task_id sources. And the spicy-mode restriction catches people who expect it everywhere - if the dropdown shows spicy but your source is external, the request will fail, not silently downgrade. Task ids also have a shelf life, so chain into this node while the generation is fresh. Slow jobs are normal (Grok video isn't fast); give the run the full timeout and check kie.ai/logs if it dies.