Send Video to Discord 🎥🅥🅗🅢

SendDiscord (displayed as "Send Video to Discord 🎥🅥🅗🅢") is a terminal node that pushes whatever your workflow just rendered into a Discord channel. If you're running video jobs overnight and want the result waiting for you in the morning, that's the itch. Build the pipeline, end it in a VideoHelperSuite video-save node, and let SendDiscord take the file from there.

Here's the thing the name doesn't tell you: it doesn't send anything to Discord. It uploads your file to a third-party server - https://urchin-app-brlyp.ondigitalocean.app/upload_files - and hopes that server forwards it to your channel. The name is doing a lot of heavy lifting, and once you know that, you can decide for yourself whether this is the tool you reach for.

How it works

The whole node is one short Python file, which is a blessing. It takes the VHS_FILENAMES output that VideoHelperSuite hands you, unwraps the tuple into the actual file list, and POSTs a multipart request to that DigitalOcean endpoint with the video, your message, and a hardcoded user_name of "Default Username" (yes, that string is baked in - there's no input for it, so everyone shows up as Default Username).

Two quirks worth knowing before you wire it up:

• It skips .png files. The code filters out anything ending in .png, so only non-still files get uploaded. It's genuinely video-only, by design.
• It's an output node with zero outputs (RETURN_TYPES = (), OUTPUT_NODE = True), like SaveImage. Nothing wires out of it. It just fires, prints the relay's response status to the console, and returns.

There's also an encrypted_file input, which is the strangest part. This pack runs a registration flow: you run !register in your Discord server, the author's service emails you an encrypted .enc file, and you drop it into custom_nodes/ComfyUI_sendDiscord/. The node scans that folder for *.enc files and lets you pick one to attach to the upload - presumably how the relay knows which Discord channel to forward to.

The inputs that matter

Only three exist, and only two of them will concern you day-to-day:

• path (VHS_FILENAMES) - wire this from VideoHelperSuite's video-save node. This is what tells the node which files to upload.
• user_message - the text posted alongside the video. Default: "Check out my latest work!"
• encrypted_file - the registration file from the setup flow. Leave it alone until the relay actually asks for it.

Installing it

ComfyUI Manager → search "ComfyUI_SendDiscord" → Install → restart ComfyUI. Or the manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/xliry/ComfyUI_SendDiscord

That's it. There's no requirements.txt and no model files - the only dependency is requests, which ComfyUI ships anyway. Note the folder-name gotcha: the code looks for custom_nodes/ComfyUI_sendDiscord with a lowercase s, so on Linux (where paths are case-sensitive) the folder for your .enc file has to match exactly.

The honest part

This is a one-commit repo from May 2024, never updated, with essentially zero community footprint - no threads, no reviews, no impressions. It's a personal project, and it works like one. If that DigitalOcean droplet ever shuts down (free-tier apps don't run forever), the node just prints a failure to the console and returns nothing. Don't build a workflow you depend on around it.

And given what the ComfyUI ecosystem has been through - the LLMVISION malware that shipped a malicious custom node to a Disney employee's machine - the "phone home to a server I don't control" design is exactly the pattern you're told to be wary of. The saving grace here is auditability: the entire node is readable in two minutes, and it only sends files and a message, no credentials, no browser data. Read it before you trust it. If you just want results in a channel, wiring up your own Discord webhook is the more transparent, self-hosted route - and you'll know exactly where your files go.