Comfyui-Kling-Wrapper Advanced Element Delete

Every node in this pack that deals with advanced elements has a job: Create registers a subject, Query checks on it, Element List Builder wires it into generation. Delete is the one nobody thinks about until they need it - you've registered a bunch of characters while experimenting, Kling is holding them all on your account, and you want to clear out the ones you'll never use.

That's this node's entire reason to exist. It's a one-input utility that tells Kling to remove an element. Dull, but if you're doing serious character work you'll accumulate cruft fast, and the API has no "manage my elements" panel you can reach from inside ComfyUI. This is that panel.

Using it

One required input, one string: element_id - the ID of the element to delete. You get that ID from Advanced Element Create or Query. Paste it in, run the node.

It's marked as an output node (OUTPUT_NODE = true), meaning it terminates a workflow branch. It does fire two outputs back for the graph's benefit:

• element_id - echoes back what you deleted, handy for logging
• request_id - the deletion request's reference from the API

Neither is essential to wire anywhere. They're there so you can, say, log which IDs you've cleaned out.

Install and gotchas

Standard pack install: ComfyUI Manager (search "Comfyui-Kling-Wrapper") or clone into custom_nodes + pip install -r requirements.txt + restart, with your Kling API key in config.local.json. API call, metered like everything else - deletion is cheap but it's not free.

The one thing to be careful about: deletion is permanent and there's no undo. If you delete an element that's currently wired into an element_list in a saved workflow, that workflow will fail at generation time with a missing-element error. Before you prune, check which element IDs your Image2Video and Motion Control workflows are still referencing. When in doubt, query the element first to see its state rather than deleting blind.

Also worth knowing: element deletion is one of the nodes the README lists as unsupported on the Vapeur provider - it fails explicitly rather than silently routing elsewhere. On the official provider it just works. It's a tiny node with a small job, but for anyone managing a character library across dozens of workflows, it's the difference between a clean account and a graveyard of expired test subjects.