3.Grok 下载视频 (Wujiai)

This is the payoff node of the Wujiai Grok video flow - 1. submit → 2. query → 3. download - the one that actually hands you the finished clip. After you've submitted a video job with GrokSubmitTask and watched it turn "succeeded" in GrokQueryTasks, this node pulls the result down and emits it as a VIDEO output your graph can use, plus a report string with the download details.

Like its sibling, it takes no required inputs. Zero required, zero optional - it just grabs "the next" finished video from the Wujiai queue and delivers it. The VIDEO output type is the pack's own media type (ComfyUI doesn't have a native video socket, so these reseller packs ship their own), and it's what you'll wire into a preview node or a save/combine step.

Why "next" and not "this one"

The name is the mechanism. The node pops the next completed video off the channel's queue rather than taking a task ID. That's actually convenient for a linear workflow - submit a job, query until done, then run this and you get exactly the one you're waiting on, because it's the only one in the queue. It gets awkward the moment you have multiple Grok jobs in flight: "next" might be a different render than the one you're thinking about. If you need surgical control over which clip you fetch, you're better off running the flow one task at a time, or relying on the report text to tell you which video you actually got.

Install & prerequisites

Same pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/jieg9341-lab/ComfyUI-nkxx

then restart (ComfyUI Manager: search "ComfyUI-nkxx"). The pack's first-launch auto-installer handles requests, pandas, openpyxl, yt-dlp, opencv-python, and aiohttp. Note the README's downloader story: it ships a yt-dlp + curl double-fallback so big files still come down on flaky networks - that machinery is exactly what runs here.

The one real prerequisite is that you've already done steps 1 and 2 with a working Wujiai key (register at wujiai.org). This node doesn't take a key field, so it relies on the key configured at the pack level - if your query node used a key that isn't set globally, the download can fail with a key error even though the query worked.

Common issues

• No video comes out: run GrokQueryTasks first and confirm the job actually completed. If it's still running, this node has nothing to hand you.
• Empty VIDEO output after a long wait: check the report string - the Wujiai side may have failed the render server-side, or the downloader fell over on a partial file. The yt-dlp/curl fallback exists for this, but a dead link is a dead link.
• Wrong clip when queueing multiple jobs: the "next" semantics, not a bug. Serialize your jobs if you need certainty.
• Trust note: the Wujiai node files are shipped obfuscated (base64+zlib exec blobs), so the downloader's actual behavior is only verifiable by watching it work. It's a fair trade for a video queue, but know what you're running.