05 Delete Gemini API Key

05 Delete Gemini API Key removes the Gemini API key from the ZMongo backend's records. It's the cleanup node for the server-side key storage this pack uses - and given that your Gemini key is stored on their server (see Save Gemini API Key), knowing how to delete it is genuinely important hygiene, not a footnote.

When would you reach for it? When you're done with ZMongo's Gemini features, when you suspect the stored key is compromised, or when you want to rotate keys - delete the old one from the server before saving the new one so there's never a stale credential sitting in their store. This is the node that answers "okay, but how do I un-leave my key there?"

How it works

One required input, session (from the 00 API Key Session node), and the usual optional gemini_prefix (default /gemini). It POSTs to /gemini/api/key/delete with an empty body. Outputs:

• json - the backend response (did the delete succeed, what message).
• success - boolean.
• refresh - a dirty token, meant to be wired into a downstream Gemini Key Status node so it re-runs and shows the post-delete state.

The refresh output is a nice touch: the intended pattern is Delete → wire refresh into Status → Status re-runs → you watch has_key flip to false, confirming the removal actually took.

Gotchas

• Deleting here is not the same as revoking in Google. This node deletes the key from ZMongo's server records. The key itself is still valid in Google's systems until you revoke it at console.cloud.google.com. If you're removing a key because it leaked, do both. The source can't do the Google-side part - it only talks to ZMongo.
• No confirmation field. Unlike Delete Collection / Delete Doc, this node has no confirm_* safety input. It just deletes. That's fine for a key (low blast radius, easily re-added), but don't wire it into an always-on graph by accident - a stray Delete node running every execution will quietly make your Gemini nodes fail until you save the key again.
• After deleting, Gemini Status will report has_key: false, and the Gemini nodes will return auth-style failures. That's expected, not a bug.

Install

ComfyUI Manager → ComfyUI-ZMongo, or:

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

restart. Thin HTTP client like the rest of the Gemini family - needs only the API session, despite the pack's heavy requirements.txt on first import.