Nodes/ComfyUI-ZMongo/09 ZMongo Content Pack Manifest Preview
ComfyUI Node

09 ZMongo Content Pack Manifest Preview

Preview what's inside a content pack before you wire it up

By CentralFloridaAttorney·Created 5 months ago·Updated 2 months ago· 1
09 ZMongo Content Pack Manifest Preview
  • content_pack
  • markdown
  • field_table_json
  • aliases
  • data_types
  • indexed
  • success

If you've ever loaded a workflow and stared at a mystery node wondering what's actually inside it, this is your answer. 09 ZMongo Content Pack Manifest Preview takes a ZMONGO_CONTENT_PACK and renders it as a readable Markdown manifest - every field, its alias, its type, where it came from, and a peek at its value. It's the debug/visibility node of the V3 content-pack family.

A content pack is just structured JSON under the hood: a normalized manifest where each field carries an alias, label, source_path, comfy_type, storage mode, and a value summary. That structure is what makes packs portable - but it's also exactly the kind of thing you don't want to read as raw JSON. This node does the reading for you.

What it does

You feed it a content_pack (from Build, Load, or any loader) and get back:

  • markdown - the human-readable manifest: pack name, project, schema version, field count, manifest hash, then a numbered list of fields with alias, type, source path, and a truncated value display.
  • field_table_json - the same info as JSON rows (index, alias, label, source_path, comfy_type, storage, summary), for when you want to feed the structure into something else programmatically.
  • aliases and data_types - the parallel alias/type lists, same index convention used everywhere else in the pack.
  • indexed - a formatted alias [type] dump.
  • success - false if you handed it something that isn't a valid pack.

When you'll reach for it

Three situations, in rough order of frequency. First, after a Build, to verify the flattening did what you wanted - did your nested prompt JSON come out with the aliases you expected, or did auto_safe drop a field you needed? Second, after a Load, to confirm you pulled the right version before wiring Get nodes. Third, when a Get node returns found: false, this is where you go to see what aliases actually exist. It takes no other inputs and needs no session - it's a pure view over whatever pack you hand it, which makes it perfect as a temporary branch off any pack-producing node.

Gotchas

Don't expect it to do anything but look. There's no editing here (the separate Alias Editor node covers that), and image fields show as a summary rather than the actual pixels - the value preview is text-only. Also note the markdown is generated from the manifest, so if a field's summary was truncated when the pack was built, you'll see the truncated version here too. For everything else, it's the fastest way to stop guessing what's in the box.

CategoryZMongo/09 Content Packs

Inputs (1)

NameTypeDefaultDescription
content_packZMONGO_CONTENT_PACK

Outputs (6)

NameTypeDescription
markdownSTRING
field_table_jsonSTRING
aliases*
data_types*
indexedSTRING
successBOOLEAN