Suno Voice Check Availability API

The whole point of this node is one number: whether the custom voice you asked KIE to build from your voice sample is actually done. It takes a single task ID and gives you the answer.

It exists because Suno voice cloning on KIE is not one call. You generate a verification phrase, you record yourself singing it back, you submit the recording to create a custom voice, and then you wait - the voice isn't instant. This node is the "is it ready" step at the end of that chain, and it's the boring one you'll be tempted to skip. Don't; the voice ID you feed into a music generation node later comes out of this pipeline.

How it works

Like every generation node in this pack, it's a thin wrapper over KIE's documented request. It submits task_id to KIE's Market task endpoint (/api/v1/jobs/createTask), then blocks and polls the record endpoint until the task reports success or failure, backing off from roughly 2.5 to 15 seconds between checks. When it comes back you get the provider's own JSON in raw_json, plus the usual credit receipt.

That's worth knowing: despite the "check availability" name, this isn't a cheap single ping. It's a wait-for-completion node wearing a status node's clothes. If you just want to peek without blocking, use KIE • Task Status instead - it does one lookup of the same record and returns state, progress and raw_json immediately.

Inputs and outputs

The only thing you must set is task_id - the task ID of the voice you're checking, not the verification-phrase task. Paste it, or wire it from the task_id output of the Suno voice creation node.

timeout_seconds defaults to 1200 with a 30–7200 range, and it's the field that actually matters on a slow day. Voice processing isn't video-generating slow, but if the provider is queueing you'll see the run fail with a timeout rather than hang forever. Bump it to 3600 if you're batching.

callback_url is for servers that want KIE to call them; leave it empty in ComfyUI, which is what the tooltip says too.

Outputs are the pack's standard seven: raw_json (what KIE actually said - read this one), task_id, url, all_urls_json, audio, credits_consumed and credits_left. Wire audio into a core Save Audio node if the response carries a playable sample, and credits_consumed/credits_left into a Show Text if you like watching the meter move.

Keep your expectations calibrated on audio: the media output is populated when KIE's response includes a URL, and these voice status endpoints don't always return one. When there's no URL to download, the node fails loudly with a "completed but returned no audio URL" style error rather than handing you an empty socket. raw_json is the honest answer to "did it work".

Install

Same pack, same one-time setup. ComfyUI Manager, search KIE.ai Nodes Next, install, restart. Manual route:

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

Requirements are genuinely light - requests, Pillow, numpy, PyYAML. No model downloads, because nothing runs locally; you're paying KIE per call. Then set your key once in ComfyUI → Settings → KIE.ai Nodes Next → Connection, paste it, and you'll get a masked fingerprint and a CONNECTED status with your credit balance. For headless installs, the KIE_API_KEY environment variable wins over the saved key.

Where people get burned

Pasting the verification-phrase task ID instead of the voice-creation task ID, then wondering why the node reports a state that never moves. Check the ID against the node that produced it.

Second: this pack builds its node list from KIE's live documentation and refreshes at most once a day, so a model or endpoint can vanish out from under a workflow when the provider retires it. That's normal for any KIE-backed graph - the community has already been through it with Sora 2 Pro disappearing off the reseller - and the fix is usually just re-running the catalog sync and pointing at whatever KIE still offers.

Third, the general one for this whole category: an API node holds your key and calls the network by design, so treat a fresh pack the way you'd treat any custom node with credentials. This one keeps the full key backend-only and stores it in ComfyUI's user/config area rather than in your workflow JSON, which is the right behaviour.