Send_to_Eagle

Eagle is the image organizer a lot of AI artists actually pay for - fast, taggable, and happy with tens of thousands of generated files. This node is the missing pipeline between ComfyUI and it: wire in your output image, give it a folder name and a description, and it lands in Eagle the moment it renders, already tagged.

What it is. Send_to_Eagle talks to Eagle's local HTTP API (default http://localhost:41595) and files your images into Eagle by folder name. If the folder doesn't exist it creates it. Each image goes in with a name prefix, a description, and comma-separated tags, plus your workflow's prompt in the metadata. It's the "I want my keepers in my organizer without dragging them across Finder windows" node.

How it works. On each run it looks up the folder via Eagle's /api/folder/list, creating it if needed with /api/folder/create. Then for every image in your batch it writes a temporary PNG into ComfyUI's output folder - with prompt and workflow metadata embedded - and POSTs it to /api/item/addFromPath. There's also a URL path: give it an image_url and it can add that instead, even converting a local ComfyUI path into an http://127.0.0.1:8188/view URL so Eagle can grab it itself. Tags come in as a comma-separated string and get split into an array. The use_direct_upload toggle exists in the UI, but read the shipped source and you'll find it's a dead parameter - the code always takes the temp-file path regardless of the switch. It's cosmetic, not a feature.

The inputs that matter. Six required, three optional:

• folder_name (STRING) - Eagle folder to file into; created if missing.
• image_name_prefix (STRING, default Comfy) - name of the item in Eagle (index is appended).
• description (STRING) - becomes Eagle's annotation.
• tags (STRING) - comma-separated; leave empty for none.
• eagle_api_url (STRING, default http://localhost:41595) - where your Eagle's local API lives.
• eagle_token (STRING) - the API token from Eagle settings (required on newer Eagle versions).
• images (IMAGE, optional) - your output batch.
• image_url (STRING, optional) - alternative to images; adds from a URL.
• use_direct_upload (BOOLEAN, optional) - see above; currently inert.

Outputs: api_log (STRING) - a full text log of every API call and its status, handy to wire into a Show Text node; and folder_id (STRING) - the Eagle folder ID it filed into.

Installing and setting up. Pack install is the usual:

cd ComfyUI/custom_nodes
git clone https://github.com/sneccc/comfyui-snek-nodes

or search "comfyui-snek-nodes" in ComfyUI Manager and restart. The real setup is on the Eagle side: open Eagle → Settings → API, enable the local server (it defaults to port 41595), and copy the token if your version shows one. If the API isn't enabled, the node can't connect no matter what you do.

Where people get burned.

• Eagle has to be running and the API has to be on. The most common failure is a connection error to localhost:41595 because the API toggle was never flipped. If you get Error connecting to Eagle API, that's the first place to look.
• Token mismatch. Newer Eagle versions require the token. The node appends it to the URL, so an expired or empty token gives a quiet 401/403 buried in the console.
• It leaves temp files behind. Every batch writes temp_0.png, temp_1.png, … into your output folder. They're not cleaned up, so a busy session accumulates junk - a minor annoyance worth knowing about before a long queue.
• Folder lookup is exact and by name. It matches folder names exactly and returns the first hit. Two folders with the same name in different branches will silently pick one.

Bottom line. The dead use_direct_upload toggle and the temp-file litter mark this as a work-in-progress, but the core flow is solid: render, file, tag, done. If Eagle is your library, this is the node that makes ComfyUI output disappear into it without you lifting a finger.