GoogleApiKeyNode

Same shape as its sibling FrankApiKeyNode, different prefix. The Google API Key Node takes the Google API key you already own and forwards it to the BananaMainNode with a GKEY- prefix, which is how the backend knows this is your own Google key rather than a resold frankAI one. Input key_input (a STRING - paste your key), output key (a STRING - wire it into BananaMainNode's key slot). The execute method is literally a string-prepend, nothing more. It doesn't validate the key, check your quota, or make any request on its own. It's a glorified label-maker.

Two things worth knowing before you rely on it.

First, the display-name bug. The pack's __init__.py tries to give this node the friendly name "Google API Key Node," but the mapping uses the wrong class key, so the pretty name never applies. In your node menu it shows up as plain GoogleApiKeyNode. If you search for "Google API Key" and find nothing, stop hunting and open the "FrankAI" category - it's sitting right there, just under its class name.

Second, the README's "use your own Google API Key" is more optimistic than reality. Nano Banana runs through the Gemini API, and a Google key that isn't set up with billing will hit quota errors almost immediately - the free tier is a few calls, not a workflow engine. The community is blunt about this: it's not free, and per-run costs accumulate faster than you expect while you're iterating on prompts. If you already pay for Gemini API access, this node is a clean way to reuse that key inside this pack. If you were hoping this was the free path to Nano Banana, it isn't - that's what the frankAI resold keys are for, and those cost money too.

Install is the pack standard:

cd ComfyUI/custom_nodes
git clone https://github.com/fr0nky0ng/ComfyUI-frankAI-banana

No models, no dependencies beyond what ComfyUI already has, just a restart. And the same security advice as the frankAI node: your key rides to a third-party server on every run, so keep it out of any workflow JSON you share.