Post to Discord w/ Webhook

Post to Discord w/ Webhook does exactly what the name says: takes the images currently sitting in your workflow and posts them to a Discord channel. You run a generation, and the finished batch lands where people are actually watching - a team server, a personal bot channel, anywhere you check Discord more often than you check your output folder. It's a delivery node, not a quality node, and if you've ever wanted your ComfyUI queue to report to you instead of the other way around, this is a three-input way to get it.

Three inputs, and you set all of them:

• images (IMAGE) - the image batch from your sampler's VAE decode output. Wire the IMAGE output of whatever decodes your latents into this.
• URL - your Discord webhook URL (default placeholder is not set, which does nothing until you replace it).
• enable (True/False) - a master switch so you can keep the node in the graph and toggle posting on and off without deleting anything.

There are no outputs; this is an output node, the end of the line. Grab a webhook URL in Discord via Edit Channel → Integrations → Webhooks → New Webhook → Copy Webhook URL. That's the whole setup - no bot token, no OAuth, no API key. The name is the mechanism: Discord webhooks are just URLs that accept a JSON POST, and the node packs your images up as attachments and fires them at the channel.

Now the part that matters, because it's the reason this node needs an article at all. The README's warning is blunt: the webhook URL is stored in the node, and node config lives inside the workflow JSON. ComfyUI culture is built on sharing workflows - you export one, post it, someone loads it. Do that with this node still in it and you have handed everyone who downloaded it the key to your Discord channel. Anyone with a webhook URL can post as it: spam, fake pings, @everyone. The author's own answer was to modify his copy so the URL is replaced with a decoy (the README mentions nyan.cat) before anything gets shared - a joke URL in the shared workflow so a leak leaks nothing. That is a fix you should copy: swap in a fake URL before you export a workflow for public consumption, or just delete the node.

Troubleshooting is mostly Discord-shaped. If the post 404s, the webhook was deleted or you lost edit access to the channel - recreate it. If nothing happens at all, check enable is True and the URL isn't still not set. And a reminder that applies to every custom node in a no-review ecosystem, per the KB: this runs arbitrary Python on import, so only install packs you're willing to read the source of. This one's tiny, which helps.

Installation is the standard two-step, shared with the rest of the Hiero-Nodes pack - search Hiero-Nodes in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Hiero207/ComfyUI-Hiero-Nodes

then restart ComfyUI. No dependencies, no models, just HTTP. If the clone 404s - the pack's repo URL was returning 404 at the time of writing, so it may have moved - ComfyUI Manager is the safer route. It's a simple node with one very real footgun, and now you know exactly where it is.