Nodes/KIE.ai Nodes Next/Suno Voice Get Custom Voice Records
ComfyUI Node

Suno Voice Get Custom Voice Records

Suno Voice Get Custom Voice Records is a placeholder — here's why, and what to do

By felipederosilva·Created about a month ago·Updated about 22 hours ago· 3
Suno Voice Get Custom Voice Records
    • audio
    • url
    • all_urls_json
    • task_id
    • raw_json
    • credits_consumed
    • credits_left
    ◄prompt►
    ◄timeout_seconds1200►
    ◄expert_override_json{}►

    This node has no inputs worth setting and doesn't work yet. I'd rather say that on line one than make you find out at run time.

    What it's supposed to be: the endpoint that lists the custom voices you've already created on KIE, so you can find a voice ID instead of archaeology through old task IDs. KIE documents it at docs.kie.ai/suno-api/suno-voice-record-info. What it actually is in this pack: the node exists, it's registered in the menu, and when you run it you get an error telling you the API page hasn't been resolved yet.

    Why a registered node can be broken

    This pack doesn't hardcode a node list. On startup it reads KIE's official API documentation index and builds one node per callable endpoint, then enriches each node from that endpoint's own page. For 241 operations in the bundled catalog that works. A handful of pages come back in a shape the parser can't turn into a request schema - sometimes the docs render client-side and the fetch returns page scaffolding instead of JSON. KIE's own summary string for this page is, literally, a blob of JavaScript from the docs site.

    So the pack registers the node - the docs URL existed, the title was readable - but it has no method, no endpoint and no parameter list to work from. When you execute it, you hit:

    This KIE API page has not been resolved yet. KIE Next will retry from
    the official docs; you can also run Refresh Live Catalog.
    

    That message is accurate. It isn't a config problem on your side.

    What the widgets are

    The input list is what the generator falls back to when a page yields no schema. prompt is a required multiline string, but read it as decorative self-documentation - there is no payload schema for it to feed. That's the same generic prompt widget the pack uses as a skeleton for unparsed generation pages, and it lands on any page whose title mentions voice, image, video or generation.

    timeout_seconds (30–7200, default 1200) is the standard wait window. expert_override_json is a {}-defaulted text field for patching request bodies on endpoints whose docs are still thin. Important caveat: it can add or fix fields in a body, but it cannot supply a missing endpoint. No amount of JSON in that widget makes this node fire a request, because the pack never learned where to send it.

    Outputs are declared as audio, url, all_urls_json, task_id, raw_json, credits_consumed and credits_left - the default media-node signature for the Suno audio family, not a promise that a voice-record listing will have any of it.

    What to do instead

    Try the cheap fixes first. Run KIE • Refresh Model Catalog and restart ComfyUI - pages do get parsed on a later pass, and this pack re-checks at most once every 24 hours. KIE • Inspect API Definition (Advanced) will show you exactly what the catalog currently knows about the operation, which is the fastest way to tell "unparsed" from "you typed the endpoint wrong".

    If it's still unparsed, go around it rather than through it. KIE • Universal Market Task (Advanced) takes a model ID plus a raw input_json and can hit any Market model KIE has discovered, and the pack's advanced raw-request node lets you name a custom_endpoint directly when you know the documented path from KIE's docs. Both are more typing than a purpose-built node, and both actually work.

    Install

    Nothing special for this one, and nothing to install locally beyond the pack itself:

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

    Restart, then set your key once under Settings → KIE.ai Nodes Next → Connection. ComfyUI Manager can install it too; search "KIE.ai Nodes Next". Requirements are requests, Pillow, numpy, PyYAML - no models, since everything runs on KIE's side and every call is metered.

    One honest framing for the category: an API-wrapper node is a network client with your credential in it, so it's the one node type worth being fussy about. This pack is the lesser-known of the KIE options - there's a separate ComfyUI-Kie-API pack doing the same job with more community mileage - so skim what any of them do with your key before you paste it.

    CategoryKIE Next/Audio/Suno/voice

    Inputs (3)

    NameTypeDefaultDescription
    promptSTRINGPrompt sent to this KIE model.
    timeout_secondsoptINT120030–7200—
    expert_override_jsonoptSTRING{}Expert-only payload overrides for APIs whose documentation has no request schema yet.

    Outputs (7)

    NameTypeDescription
    audioAUDIO—
    urlSTRING—
    all_urls_jsonSTRING—
    task_idSTRING—
    raw_jsonSTRING—
    credits_consumedFLOAT—
    credits_leftFLOAT—