D2 Send File Eagle

D2 Send File Eagle exists to answer one specific question: "how do I get my finished video into Eagle without digging through the output folder by hand?" Eagle is a desktop asset manager - think of it as a searchable, taggable library for images, and yes, it handles video too. This node takes a file path, registers that file into an Eagle folder, and optionally attaches a memo. It's the text-only cousin of D2 Save Image Eagle, which handles images generated inside ComfyUI. This one is for anything that already exists as a file on disk.

Why it exists

The pack's own docs are honest about the use case: it was built to register the output of a Video Combine node. Video outputs don't flow through the image-save nodes, so you end up with an mp4 sitting in ComfyUI/output and a manual drag into Eagle. This node kills that step. Wire the file path from your video combine into file_path, run it, done.

How it works

file_path takes a string or a list of strings - so you can pass one path, or an array of paths from a folder-queue style node and register a whole batch. eagle_folder can be either the folder name or its ID; if a folder by that name doesn't exist yet, the node creates it for you. memo_text is a free-form note that becomes the item's annotation in Eagle - the docs show using D2 Filename Template2 to build a "Steps, sampler, seed, model" text block and passing it in here.

Under the hood it talks to Eagle's local HTTP API, which means one absolutely critical prerequisite: Eagle has to be running with its API enabled. The node hits http://localhost:41595, Eagle's default API port. If Eagle isn't open, or the API toggle in Eagle's settings is off, the request fails and the node errors out - it doesn't silently queue anything.

The inputs, briefly

Only three, and they're all simple:

• file_path - full path to the file, or a list of paths. The "any" type means it accepts whatever you feed it.
• eagle_folder - folder name or ID. Blank sends to wherever Eagle defaults.
• memo_text - annotation text, multiline. Optional.

There are no outputs; this is a terminal node.

Installing and troubleshooting

It's part of D2 Nodes ComfyUI, so you're installing the pack, not a standalone node:

cd ComfyUI/custom_nodes
git clone https://github.com/da2el-ai/D2-nodes-ComfyUI

or search "D2 Nodes ComfyUI" in ComfyUI Manager. The Eagle integration needs nothing extra installed - the pack talks to Eagle over HTTP with plain requests. The failure modes you'll actually hit, in order: Eagle not running, API not enabled (Eagle → Settings → API → enable local HTTP server), and a path Eagle can't read because it's not a path Eagle has access to. That last one is sneaky - if ComfyUI and Eagle run on the same machine it's usually fine, but a path that only makes sense inside a container or over a network share will produce a cryptic "request failed." Check the path is a real local absolute path before you suspect the node.

If your images (not videos) are the thing you're sending, D2 Save Image Eagle is the better node - it saves and registers in one step and can auto-write the full A1111-style generation parameters into the memo. This one's for the files that don't go through a save node.