Get Task Details

What it is

Despite the node ID - which reads like a Grok Imagine text-to-image class - this is Get Task Details, the KIE pack's generic "look up a job" utility, filed under KIE Next / Utility. It calls KIE's common task-record endpoint and hands you the JSON: state, progress, result URLs, failure message. Nothing is generated, nothing is charged for a model, and no credits are at stake beyond the API call itself.

The name mismatch is an artefact, not a bug in your eyes: the pack builds one node per documented API page, deriving the internal class ID from the page path plus the model it was filed under, while the menu shows the page's title. KIE's shared "get task detail" documentation happens to be indexed against a Grok Imagine model string, so the class name inherited it. It does not call Grok.

Why you'd want this at all: when a paid job behaves strangely - a video node returns an error, a task seems stuck, credits vanished and you don't know what for - this node is how you look under the hood instead of guessing. Debug tooling for the API layer is the thing most wrapper packs skip.

How it works

The endpoint behind it is a GET (KIE's /api/v1/jobs/recordInfo shape), and the pack's handling of GET operations is specific and worth knowing: whatever you put in expert_override_json is sent as query parameters, merged over anything the schema provides. That's the documented escape hatch for this node, because the page this node was generated from publishes an example but not a parameter table - so the pack couldn't synthesize a friendly taskId widget, and the override is how you supply it.

So, in practice:

{"taskId": "the_task_id_from_another_node"}

Paste a task ID from any generation node's task_id output, put it in that JSON, run the node. The pack then fetches the record, and the three outputs are filled from the response.

Inputs and outputs

The only widget is expert_override_json - a multiline string defaulting to {}, described by the author as "expert-only payload overrides for APIs whose documentation has no request schema yet". For this node it's the input, not the last resort.

Outputs: raw_json is the whole record pretty-printed, which is what you actually came for; first_url is the first result URL the record exposes, if there is one; task_id is the ID the pack extracted from the response (KIE records carry it as taskId/task_id/id), so it echoes your lookup back for chaining. Failures show up as an explicit error with the provider's own message rather than a silent empty string - the pack's client raises with the payload attached, which is exactly the behaviour you want from a debugging node.

Where it fits with the rest of the pack

This is the low-level end of a node collection that otherwise hides all of this: the README keeps "task status/wait and upload/download helpers" under Utility and puts market and inspection tools under KIE Next / Advanced, where you'll also find a universal market-task submitter and an API-definition inspector. Beginners should never need them; when API work misbehaves, they're the difference between "it broke" and "KIE returned failMsg: ...".

Install

Manager → KIE.ai Nodes Next, or git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next into ComfyUI/custom_nodes and install that folder's requirements.txt in ComfyUI's Python. Dependencies: requests, Pillow, numpy, PyYAML. Restart, then save your key once at Settings → KIE.ai Nodes Next → Connection (KIE_API_KEY for headless). The pack regenerates its node list from KIE's docs index on first launch and re-checks roughly daily, reloading the frontend once.

Gotchas

• The JSON must parse. A malformed override string fails locally before any request is made - annoying, but free.
• Task records expire, and so do tasks. Ask about a job from last month and you may simply get an empty or failed lookup; that's the provider's retention, not the node.
• It doesn't fix anything. Useful diagnostic, zero generative value. Don't expect a retry mechanism.
• Search for it by display name, not class. In the ComfyUI add-node menu it's Get Task Details under KIE Next / Utility; the class ID will not help you find it.
• No key → No KIE API key configured. - the one-time Settings step.