Vertex Load Config

The "import" half of the pack's config system, and the laziest way to get back into a workflow you've already set up. VertexLoadConfig lists the JSON files in the pack's config/ folder and hands you a dropdown. Pick one, and it outputs the vertex_config and generation_config that were saved inside it.

It's the node you reach for when you've saved a setup with VertexSaveConfig (or auto-saved one via VertexAIAuth) and want to rebuild a workflow without re-entering credentials, project IDs, or your carefully tuned sampling parameters. It's also the least typing-intensive path in the whole pack: no filename, no path - just a menu.

How it works

When the node is created, it scans the config/ directory for *.json files and builds its dropdown from them. Pick one and it loads the file, then splits it into two outputs:

• vertex_config (VERTEX_CONFIG) - credentials + project settings, the same thing VertexAIAuth produces. Wire it into the generators' vertex_config input and you've replaced the auth node entirely for that workflow.
• generation_config (GENERATION_CONFIG) - the saved sampling parameters, ready for a generator's generation_config input.

Two things to know. First, the dropdown is populated when the node is added - if you save a new config with VertexSaveConfig afterward, it won't appear until you add a fresh VertexLoadConfig node or reload. Second, if the folder is empty the dropdown shows none, and running it returns empty {} configs - which will hand your generators nothing and produce an error on the next call. It's a graceful-enough failure, just not an obvious one.

Installing it

Same pack, same route: ComfyUI Manager → search comfyUI_Vertex_API, or

cd ComfyUI/custom_nodes
git clone https://github.com/linfen0/comfyUI_Vertex_API.git
cd comfyUI_Vertex_API
pip install -r requirements.txt

then restart ComfyUI.

The honest take

This is the most pleasant node in the pack to use and the easiest to overlook. If you're starting a new workflow from a saved one, drop this in, pick the file, and both config wires are handled in one click. The only real complaints are the load-time-only dropdown and the silent empty-config path - both minor, both easy to work around once you know they exist.