ComfyUI Node

00 Health

The 'did the database still wake up' node — ZMongo 00 Health

By CentralFloridaAttorney·Created 5 months ago·Updated 2 months ago· 1
00 Health
  • session
  • json
  • success
refresh_token

00 Health is the node you wire up first when you can't tell whether ComfyUI-ZMongo is even talking to anything. It takes a session and asks the backend "are you alive?", then hands you a json payload and a success boolean. That's the whole job. Boring, and that's exactly why it's worth having: when every other ZMongo node is failing with some vague error, this one tells you whether the problem is the connection or the node.

ComfyUI-ZMongo is a database layer for your graphs - a prompt hub and parameter store where you save and load values by dot-path instead of hardcoding them. Every data node in the pack needs a session, which comes from one of the two "00" session nodes: 00 API Key Session (hosted backend, needs an API key) or 00 Local File Store Session (zero-config, writes JSON to a local folder). Health is the smoke test for whichever one you chose.

How it works

The node calls session.health() on whatever session you feed it. If the session object is None - say you forgot to wire one in - it short-circuits and returns a payload with an error message and success: false, which is a nicer failure mode than a hard crash. If the session is real, the backend responds and the node reflects the success flag from that response straight to its success output.

It's tagged AlwaysDirty, like the rest of the pack, so it re-runs on every execution - no stale cached health results.

The inputs and outputs that matter

  • session - the only required input, type ZMONGO_API_SESSION. Wire it from a session node.
  • refresh_token - optional string, part of the pack's cache-busting plumbing. Ignore it on a first pass; it's there so downstream nodes can tell data changed.

Outputs are json (the raw response, handy for a text preview node) and success (a boolean you can feed into a switch or gate node). With a healthy local file store session, you get a success payload that includes things like the store root directory; against the hosted API you get server status.

Install

Find it under ZMongo → 00 Auth once the pack is in. ComfyUI Manager is the easy path - search "ComfyUI-ZMongo" and install, then restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/CentralFloridaAttorney/ComfyUI-ZMongo
cd ComfyUI-ZMongo
pip install -r requirements.txt   # heavy; see note below

The README's short install line is just pip install pymupdf python-docx requests python-dotenv, but the repo's actual requirements.txt pulls in a lot more - pymongo, pandas, langchain, sentence-transformers, transformers, FlagEmbedding, pymilvus, tkhtmlview and friends. Those are for the pack's embedding, vector-search, and OCR features. For plain database CRUD you really only need the HTTP/persistence core, but letting Manager install the full set is the most reliable way to get a complete pack.

Troubleshooting

  • success: false with "No session provided." - you left the session input unconnected, or wired it from the wrong output. Health is the fastest way to confirm this.
  • Hosted API returns failure but local works - check the API key in your 00 API Key Session node and that the base URL is reachable. Remember the fallback: with no credentials, the pack happily runs in local file store mode, so "working" and "connected to the hosted silo" are two different things.
  • Local file store location - with a 00 Local File Store Session using a blank root, data lands in custom_nodes/ComfyUI-ZMongo/nodes/local_store. Useful when you later wonder where your JSON went.

If Health passes, the connection isn't your problem - go check the specific node you're running.

CategoryZMongo/00 Auth

Inputs (2)

NameTypeDefaultDescription
sessionZMONGO_API_SESSION
refresh_tokenoptSTRING

Outputs (2)

NameTypeDescription
jsonSTRING
successBOOLEAN