Image Send HTTP

Most nodes end a workflow by writing a file to disk. Image Send HTTP ends it by shipping the image somewhere over the network instead - it sends your generated image to an HTTP endpoint you specify. If you're wiring ComfyUI into a larger system - a bot, a webhook, a backend that collects results - this is the node that pushes the output out to that service the moment a run finishes.

Straight up: this is a niche, integration-focused node, and one of the less-documented corners of the pack. If you're a beginner making images to look at, you don't need it. If you're automating ComfyUI as a piece of something bigger, it's the difference between polling the output folder and getting the result delivered.

How it works

When the graph runs, the node takes the image and transmits it to the URL you've configured over HTTP, rather than (or in addition to) saving locally. Practically, it turns a finished render into an outbound request - the receiving endpoint gets the image and does whatever it does with it (store it, forward it, display it). That makes it a terminal node in the same family as Image Save: the end of the pipeline, just pointed at a server instead of a disk.

The honest caveat: this node isn't in the pack's main README node list, and it draws essentially zero community discussion, so treat the exact request shape and options as something to confirm by inspecting the node in your own ComfyUI rather than from documentation. What's reliable is the intent - get an image to an HTTP endpoint from inside a workflow.

Inputs and outputs that matter

The core inputs are the image to send and the destination URL/endpoint it posts to. Because it's a delivery node, the meaningful "output" is the side effect - the request landing at your endpoint - not a wire you chain onward. Check the node's own fields in the editor for anything else it exposes; given how thinly this one is documented, that's the trustworthy source.

How to install it

ComfyUI Manager: search was-node-suite-comfyui, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

then install the pack's requirements.txt in your ComfyUI venv and restart. HTTP sending relies on a requests-style HTTP library that comes with the pack's requirements - no models to download.

Common issues & troubleshooting

Nothing arrives at the endpoint. Start with the URL and the receiver. Confirm the endpoint is reachable from the machine running ComfyUI (not just from your laptop), that it's actually listening for the method and content type the node sends, and that no firewall is eating the request. Test the endpoint with a plain curl first so you know the server side works before blaming the node.

It errors or times out. A slow or unreachable endpoint will stall or fail the send. Make sure the receiver responds promptly; a hanging server hangs the node.

Security reminder. You're sending image data out over the network - point it only at endpoints you trust and control, and don't expose the receiving service carelessly. The ComfyUI ecosystem KB is emphatic that ComfyUI's own surfaces are unauthenticated by default and shouldn't be left open; the same caution applies to anything you're POSTing renders into.

It's undocumented and I can't tell what it expects. You're not missing anything - this node genuinely lacks public docs and community write-ups. Read its inputs directly in the node editor, and if it doesn't fit your integration, a small custom node or an external script that watches the output folder is a common alternative.

Whole pack won't import after a ComfyUI update. The standard WAS Node Suite issue - package downgrades vs a ComfyUI bump breaking the startup import. Re-run the pack's requirements against the activated venv, or install.bat. Maintenance-only since late 2023.