NGs Discord - Webhook Send

The use case here is boring in the best way: you kick off a long batch, walk away, and want a ping in your Discord server the moment it's done, with the image right there, instead of tabbing back to poll a queue. That's exactly what this node does - hand it an image and a webhook URL, and it posts. It's a small, focused idea, and it's one other people in the ComfyUI community have independently built too, which tells you it's a genuinely common thing to want, not a NeoGriever-only quirk.

Worth flagging up front: this node isn't in the pack's own README at all - not in the table of contents, not anywhere. The category (NeoGriever/Communication) doesn't appear in the documented node list either. Everything below is read directly off the node's schema, not confirmed by author prose.

How it works

It's marked as an output node, meaning it can be a terminal point in your graph on its own - you don't strictly need a separate Save Image node alongside it, though there's nothing stopping you from using both. It POSTs the image to whatever webhook_url you give it. If your image carries transparency and you don't want Discord's default background showing through oddly, add_background flattens it onto a solid color first.

The inputs and outputs that matter

• image - what gets posted.
• webhook_url - the URL Discord generates for a channel under Server Settings → Integrations → Webhooks.
• add_background (optional, off by default) and background_color (optional, default #000000) - flatten transparency onto a solid color before posting, if you want that.

Outputs: image (passthrough), msg_id (the Discord message ID), and discord_image_url (the CDN URL Discord assigned the upload) - useful if you want to log it or chain something else off the post.

How to install it

ComfyUI Manager: search "NeoGriever," install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/NeoGriever/ComfyUI-NeoGriever

then restart. No dependencies beyond what the pack already needs.

Common issues & troubleshooting

Treat the webhook URL like a password. Anyone who has it can post to your channel - Discord doesn't ask for any other authentication. Don't leave it sitting in a workflow JSON you hand to someone else, and regenerate it in Discord's settings if you think it's leaked. This isn't specific to this node - it's just how Discord webhooks work in general - but it's worth being deliberate about, because ComfyUI's custom-node ecosystem has no code review or sandboxing at all. The 2024 ComfyUI_LLMVISION incident, where a malicious node exfiltrated user data through a Discord webhook, is the extreme version of exactly this attack surface - different node, same mechanism, and a good reminder that anything you type into a text field in a workflow graph is visible to whatever code that node runs.

Nothing shows up in the channel. No validation of webhook_url is documented, so a malformed or deleted webhook likely just fails silently or errors on the POST - double-check the URL is current (regenerating a webhook in Discord invalidates the old one).

Large batches or big images failing. Discord webhooks have their own attachment size and rate limits independent of anything in this pack - keep single posts reasonable and avoid hammering the same webhook in a tight loop.