Get AI Video Details

What it's for

Here's the thing that confuses people about this whole family of nodes: normally you don't need them. When you run a KIE generation node in this pack, it submits the job, waits for it, and hands you the video. The node is the polling loop.

Get AI Video Details is the other half of that pattern, exposed as its own node. It queries Runway's task-record endpoint for a task you already know the ID of. That's useful in exactly three situations: you submitted the job from outside ComfyUI (the kie.ai dashboard, n8n, a script), another workflow created the task and you're picking up the pieces, or you deliberately submitted with a callback URL and want to come back and read the result later.

It's the pack's read-only window into a KIE task. No generation, no charge, but also no magic: it can only tell you about a task that exists.

Runway, for context, is one of the closed video models with no open weights, so there's no local fallback here - that's the usual deal with API nodes. You call it or you don't have it.

How it works

The node hits Runway's record-detail endpoint (/api/v1/runway/record-detail in the bundled catalog) with your saved KIE key and returns the task record as JSON. The pack already knows how to read Runway's status field internally - its wait loop expects a state value and treats success as done, fail/failed as terminal - so the plumbing understands this API family rather than blindly proxying it.

One honest caveat about this specific node. KIE's page for it didn't publish a machine-readable request schema when the pack built its catalog, so the node was generated from the fallback path. The consequence is visible in its inputs, and you should know about it before you queue it.

Inputs and outputs

Required: prompt - a STRING with the tooltip "Prompt sent to this KIE model." That tooltip is the pack's generic placeholder text for nodes built from documentation pages without a request schema, and it's the giveaway that this field isn't a real parameter of a status lookup. A record-detail call doesn't take a prompt.

So where does your task ID go? Into expert_override_json (optional, defaults to {}) - the pack adds this escape hatch precisely for pages whose docs lack a schema. On a GET node like this one, keys in that object are sent as query parameters, so a payload like {"taskId": "your-task-id"} is how you actually ask about a task. Leaving it at {} and filling in prompt gets you a request that asks for nothing in particular.

The pack also re-resolves documentation on demand: when a node is opened or run, an unresolved page is re-fetched from KIE's docs. So after a UI reload or a catalog refresh this node may pick up its real documented fields and stop looking like a placeholder. If it does, use them.

Outputs are video (VIDEO), url and all_urls_json (STRING), task_id (STRING), raw_json (STRING), and the two floats credits_consumed and credits_left. Treat this as metadata: the payload you care about is in raw_json, with url giving you the first extracted link if there is one. The socket names come from the API family's media kind, not from a promise that a status call will hand you fresh pixels.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next
pip install -r ComfyUI-KIE-Nodes-Next/requirements.txt

Restart ComfyUI. The dependencies are requests, Pillow, numpy and PyYAML - no torch extensions, no checkpoints, no GPU time, because this is an HTTP client over KIE's API. Then set your key once: Settings → KIE.ai Nodes Next → Connection → Paste / replace KIE.ai API key. The pack verifies the key before saving it and shows a masked fingerprint, so a typo shows up immediately. Server installs can set KIE_API_KEY instead, which wins over the saved value. Windows users can run the one-click installer from the repo's dist/ folder; it finds Desktop and Portable installs for you.

Where people get burned

The placeholder prompt field is the number one source of "this node does nothing" reports in packs shaped like this. If you're passing a prompt to a status endpoint, nothing is being queried.

Second: a failed task comes back as an exception, not a tidy error object - the pack raises on terminal failure states and includes the provider's own message. Read the message; KIE's failures are usually specific.

Third, the whole-pack caveat: a node that calls the network with your key is the one place where odd behaviour looks normal, and this category has shipped malware before. Prefer packs you can read, and note that this one at least keeps your key in ComfyUI's user config directory rather than in the workflow JSON.