Nodes/ComfyUI-ZMongo/09 ZMongo Content Pack JSON Text Loader
ComfyUI Node

09 ZMongo Content Pack JSON Text Loader

Load a content pack straight from pasted JSON text

By CentralFloridaAttorney·Created 5 months ago·Updated 2 months ago· 1
09 ZMongo Content Pack JSON Text Loader
    • content_pack
    • json
    • manifest_json
    • aliases
    • data_types
    • indexed
    • success
    content_pack_json{}
    validate_schematrue
    refresh_token

    The lightest way into the content-pack system: paste a JSON string into a text input and get a fully working ZMONGO_CONTENT_PACK out. No file on disk, no database, no session. If Load JSON File is the "I have a file" importer, this is the "I have text in my clipboard" importer.

    It exists because in ComfyUI the cheapest way to ship data around is often just a string in a widget. Someone posts a pack as JSON in a chat, or you've got a pack serialized inside another node's output - you paste it into content_pack_json, and the loader parses it into a real pack. Since the input is multiline: true, there's no fighting to get a big JSON blob into a one-line field.

    Inputs

    • content_pack_json - the JSON text. The loader accepts a bare portable envelope or a pack embedded in a workflow JSON, so both common formats work.
    • validate_schema (default true) - checks schema_kind before importing. On, and a non-pack blob is rejected with a clear message; off, and it force-coerces whatever you give it.

    That's it. No other inputs, and notably no image_policy - unlike the file loader, this node has no way to ignore or require image data, so whatever images the text carries (usually inline base64) just come through. If you need the image-policy controls, use Load JSON File instead.

    Outputs

    Same standard set as the other loaders: content_pack (the thing you wire into Get nodes), json (the rehydrated document), manifest_json, the parallel aliases and data_types lists, indexed (the alias [type] dump), and success. On failure you get an empty pack, success: false, and the error message in the json output.

    Where it fits

    This is the node to reach for when you're building a reusable workflow template that should accept a pack from anywhere - another node's string output, a text block, a previous export. It's also the friendliest way to test a pack someone shared in text form before you commit to saving it to the database. One caveat: it validates on import, so a pack with a schema version you haven't seen gets the same treatment as garbage - check the message in json if success comes back false. Fully offline, zero credentials, and it makes the portable side of the pack genuinely portable.

    CategoryZMongo/09 Content Packs/Portable

    Inputs (3)

    NameTypeDefaultDescription
    content_pack_jsonSTRING{}
    validate_schemaBOOLEANtrue
    refresh_tokenoptSTRING

    Outputs (7)

    NameTypeDescription
    content_packZMONGO_CONTENT_PACK
    jsonSTRING
    manifest_jsonSTRING
    aliases*
    data_types*
    indexedSTRING
    successBOOLEAN