VNTANA List Pipelines

VNTANAUpload3DModel refuses to run without a pipeline_uuid - the ID of the optimization pipeline that processes your uploaded model on the VNTANA side. VNTANAListPipelines is how you get one. It takes your credentials and returns two parallel lists: pipeline_uuids and pipeline_names, covering every optimization pipeline your organization has.

What it's for

If you think of VNTANAUpload3DModel as "hand the model to VNTANA's processing," the pipeline is the which processor - web output, high-quality output, whatever your workspace has configured. The upload node needs a concrete UUID, and this is the discovery step that produces it:

VNTANACredentials → VNTANAListPipelines → pipeline_uuid → VNTANAUpload3DModel

Wire the two List nodes' outputs together by position - name list and UUID list line up - pick the pipeline whose name matches what you want, and feed the UUID in. Once you've found it, you can hardcode it later, same as product UUIDs.

One honest quirk

The README claims this node has an optional workspace_uuid input for scoping pipelines to a workspace. The shipped code doesn't have one - the schema is just credentials in, two lists out. It lists pipelines across your whole organization, full stop. If you're on a multi-workspace org and the list feels broad, that's why. Not a bug, just a doc-vs-code drift worth knowing about.

It's a read-only, no-config node: credentials in, pipeline_uuids and pipeline_names out. Nothing else to set, nothing to get wrong.

Install

Standard for this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/VNTANA-3D/vntana-comfyui-node
cd vntana-comfyui-node
pip install -e .

Restart ComfyUI, or install via ComfyUI Manager under "vntana-comfyui-node". No models, no heavy dependencies.

Troubleshooting

• Empty pipeline list - your organization has no optimization pipelines configured (or your account can't see them). Check the VNTANA platform; there's nothing this node can do about missing config.
• Upload node still complaining about pipeline - you either fed it a UUID from the wrong org, or you typed it by hand and mangled it. Re-run this node and copy-paste instead.

That's it - a two-line discovery node that exists because a pipeline UUID is the one piece of VNTANA config you can't guess. Run it once, note the UUID, move on.