MiniMax H3 List Tasks

Every generation this pack submits becomes a record on MiniMax's side, and - unlike most of what happens in ComfyUI - those records outlive your session. MiniMax H3 List Tasks is the only node here that shows you that history. It's the accounting desk: what did I run, what did it cost me in wall-clock and credits, and which of those task IDs do I still care about.

It's an output node, so it executes when you hit run, and it hands you two things: items_json - the raw array of task records as a JSON string - and total, an integer count matching your filters.

The filters

page_num (1–100000) and page_size (1–100) do what you'd think, and page_size defaults to 20. status filters across all, queued, running, succeeded, failed and cancelled; task_type narrows to all, generation, h3_context_ir or regeneration. Picking all simply drops the filter from the request rather than sending the literal word, which is why all behaves like "no opinion" instead of an error.

task_ids is a multiline box that takes one ID per line, or a JSON array if you prefer to paste one in - blank lines are ignored, so trailing newlines won't break it. And model is a free-text field defaulting to MiniMax-H3; change it to MiniMax-H3-Max, MiniMax-H3-Max-Turbo or MiniMax-H3-Fast to see only that tier's jobs. Leave it empty if you want everything.

That model field is more useful than it looks. It's the cleanest way to answer "how much of my bill was Max reference-video runs" before you decide whether that habit is worth keeping.

What you do with the output

items_json is a string, not a table. ComfyUI has no native grid to drop it into, so the practical move is to wire it into whatever JSON or text-display node you already use, or save it to a file and read it in an editor. It's the same payload the API returns, so every field the API documents is in there.

The real workflow is two-step: list, then act on an ID. Paste a task_id from the listing into Query Task to pull the video URL, or into Cancel Delete Task to kill or remove it. That pairing is how this pack is meant to be driven - no dashboard, just nodes that hand each other IDs.

total is genuinely useful as a single number: it counts matching records, so a filter set to failed gives you a failure count for the window, and a filter on task_type: h3_context_ir tells you how many prompt rewrites you've burned through.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/magicwang1111/ComfyUI-MiniMax-H3-API

Restart ComfyUI, then cp local.example.json local.json in the pack directory and add your api_key, with base_url set to https://api.minimax.cn or https://api.minimax.io according to your account's region. The pack needs only requests and Pillow. Nothing is downloaded, and nothing runs on your GPU. ComfyUI Manager: search ComfyUI-MiniMax-H3-API.

Things that surprise people

First, an empty items_json does not mean nothing happened - it means nothing matched. Change status back to all before you conclude your tasks disappeared.

Second, task_ids and model are both plain strings with nothing validating them, so a typo silently returns nothing instead of complaining. If a list comes back empty and you know the tasks exist, this is the first place to look.

Third, this hits the network on every execution, so it's not free of consequences for a workflow you run in a loop - list pages when you want to look, not as a step in every render.

Finally, the listing window is short. Records are only queryable for about seven days, so treat this as a recent-activity view, not an archive. If you want a permanent log, items_json is a string - write it somewhere yourself.