Zhenzhen_nano_banana_fal

Comfly_nano_banana_fal ("Zhenzhen_nano_banana_fal") is the oldest FAL-route Nano Banana node in the pack, and its model list preserves a distinction that's easy to miss: nano-banana is the text-to-image model, and nano-banana/edit is the image-editing model. They're billed separately - the changelog notes that edit jobs carry an extra image-upload fee - so the dropdown isn't a style choice, it's a pricing choice. Pick the plain model for generation, the /edit one when you're actually editing.

It's a FAL-class node in the T8mars/Comfyui-zhenzhen pack, the "Comfly" API-wrapper family that calls the author's paid reseller service. FAL billing is pre-deduct (credits held up front, settled after), and the key goes into an apikey field on the node. Same submit → poll → download machinery as every FAL node here, with the result landing as an IMAGE.

The inputs

• prompt - required, your instruction.
• model - nano-banana or nano-banana/edit.
• num_images - 1 to 4. Batch candidates in one call.
• seed - a real FAL seed (0–65535, 0 = random).
• image_way - image or image_url, how reference images are passed to the edit model.
• image1–image4 - references for edit jobs.
• skip_error and apikey.

That's the whole surface. No aspect ratio field, no resolution switch, no output-format enum - this is the minimal FAL Banana node, closer to the raw API than its newer siblings.

Outputs

• image - the result as an IMAGE.
• response - the raw API payload (and where the hosted URL lives if you need it).

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen
# restart ComfyUI

Or ComfyUI Manager → "Comfyui-zhenzhen", then a key from the author's site into apikey.

The honest part

This node is the "I remember when" entry in the Banana family. It's minimal, it works, and if you have an older workflow that references it, it still runs. But the newer FAL node (Comfly_nano_banana_2_fal) and the direct Google-class nodes give you aspect ratios, resolutions, more reference slots, and more control for the same model family. Keep this one in the back pocket for when you want the smallest possible surface and the clearest pricing - the separate text-vs-edit model split is genuinely clearer here than anywhere else in the pack. Just don't expect it to do what the newer nodes do.