Workflow Metadata (VixUI)

VixUiWorkflowMetadata is the boring node that makes the whole Visionatrix thing work, and the README is blunt about it: it's mandatory for every flow. Visionatrix reads this node's fields to know what your workflow is called, who made it, what it does, and how it should behave - and without it, your flow simply doesn't show up in the Visionatrix UI list as a usable entry.

Everything else in this pack marks inputs as controls. This node marks the workflow itself. It's not a computation node at all - in plain ComfyUI it does nothing but sit there. Its entire job is to carry the metadata Visionatrix consumes when it ingests the workflow.

Inputs that matter

The required set is the identity card:

• name - the flow's internal id, stable and machine-friendly (e.g. flux-portrait). Visionatrix uses this to key the flow.
• display_name - the human name shown in the flow list ("Flux Portrait").
• description - what it does, shown to users before they run it.
• author - you, or your handle.
• homepage, documentation, license - links and licensing. Leaving license empty on a published flow is asking for trouble; the community treats licensing as part of sharing.
• tags (default '["general"]') - JSON array of search tags, e.g. ["flux","portrait","inpaint"].
• version (default "1.0.0") - bump it as the flow evolves.

The optional set is capability flags Visionatrix uses to render the run page:

• requires (default "[]") - JSON list of extra requirements, e.g. other custom nodes.
• is_seed_supported / is_count_supported (both default true) - whether the UI offers seed and image-count controls.
• is_translations_supported (default false) - enable UI translation support.
• is_macos_supported (default true), required_memory_gb (default 0.0) - compatibility notes for the flow browser.
• remote_vae (default false) - whether the flow can use a remotely-provided VAE (relevant to Visionatrix's handling of VAE on some setups).
• long_description (multiline) - a fuller write-up beyond the short description.
• hidden - hide the flow from the UI.

Outputs

One STRING output, but you won't wire it anywhere. The real "output" of this node is the metadata itself, read statically by Visionatrix when it loads the workflow. Don't spend time routing the string.

How it works

Mechanically it's a pass-through node. Visionatrix parses the workflow JSON, finds the VixUiWorkflowMetadata node, and treats its input values as the flow's manifest. That's why it's mandatory: no metadata node, no manifest, no flow.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/Visionatrix/ComfyUI-Visionatrix

Restart ComfyUI, or install ComfyUI-Visionatrix via ComfyUI Manager. No model downloads; deps are torch, pillow, numpy.

Gotchas

The biggest mistake is treating this as optional and then wondering why your flow is invisible - it's not optional, full stop. Second: tags and requires are JSON, not comma lists; ["general"] works, general doesn't. Third, name should be stable once you publish - rename it later and existing links and saved configs for that flow break. Set author, license and version before you publish, because retrofitting identity metadata onto a flow people already use is a pain.