List ComfyUI node types with a fixed reference and useful compatibility questions

Choose a file whose unknown type is deliberate

Download private-fields.json. It is a project-authored API prompt containing CheckpointLoaderSimple, CLIPTextEncode and the fictional Synthetic-Ada-PrivatePlugin. Each appears once. The fixture's names and paths are invented so you can inspect a real saved structure without sharing a personal workflow.

The viewer compares type names with a fixed catalog derived from the official base nodes.py at ce1e922d8623. A type outside those 65 names may belong to another version, a core extra, a frontend feature or a custom implementation. Catalog absence alone does not establish which explanation applies.

• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.
• Official base-node definitions at fixed revision ce1e922d8623 — The site's reference catalog contains the 65 names in this revision's base NODE_CLASS_MAPPINGS. Core extras, frontend-only nodes, custom installations and later revisions are outside its scope.

Read and export the actual inventory

1. Step 1

   Open the JSON directly

   Open the local workflow viewer and choose private-fields.json. Expect api-prompt with three node entries and one stored connection. The file is read as JSON; none of its nodes or saved paths is executed.

   Open the JSON and node-type viewer

2. Step 2

   Find the catalog comparison

   Scroll to Node types and compatibility questions. CheckpointLoaderSimple (1) and CLIPTextEncode (1) are in catalog. Synthetic-Ada-PrivatePlugin (1) is outside catalog. Record the exact spelling and count alongside the revision, rather than converting the unknown result into a missing-plugin claim.

3. Step 3

   Locate the unknown node's actual saved inputs

   Use Filter node type to select Synthetic-Ada-PrivatePlugin, then expand Stored inputs or Original node JSON. The unknown input values remain readable, but their semantics are not inferred. Clear the filter to return to all three entries.

4. Step 4

   Save a scoped list

   Click Download reference list or Copy reference list. comfyui-references.json includes nodeTypes, counts, catalogKnown values, the fixed catalog source and compatibility questions. It also includes resolved resource strings: inspect the entire report for private paths before sending it.

Ask an answerable compatibility question

For the fictional unknown type, ask: which implementation and exact version supplies Synthetic-Ada-PrivatePlugin, and does that version support these saved inputs? Include the workflow's role, the catalog revision and any relevant static diagnostic. Ask the provider for an authoritative source rather than constructing a repository URL from the type name.

If you need a support handoff without the fictional identity, unknown type name or model path, create the separate default support report instead. It uses aliases and omits those input values; it is not a replacement workflow and cannot be imported as one.

• Prepare a previewed support document — Default aliases reduce what is copied into the report; original JSON remains unchanged.

Handle empty and unreadable input without inventing missing nodes

Try empty workflow in the viewer for a supported empty graph with no type entries. Try unrelated JSON for an unrecognized shape, or malformed JSON for a syntax failure. These are different outcomes: neither an unreadable document nor an unknown shape is a complete zero-dependency inventory.

The direct viewer accepts UTF-8 JSON up to 5 MiB and bounds inspection to 1000 nodes, 10000 links, depth 64 and 150000 values. A limit stop is incomplete reading. It does not certify that unseen entries have no custom nodes. The inventory never scans installed plugins or confirms a model is available.

• Check the implemented structural subset — Node catalogs and saved-structure diagnostics answer separate questions.

Sources and reproducible inputs

• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.
• Official base-node definitions at fixed revision ce1e922d8623 — The site's reference catalog contains the 65 names in this revision's base NODE_CLASS_MAPPINGS. Core extras, frontend-only nodes, custom installations and later revisions are outside its scope.