Send to Work WeChat

This node is exactly what the README's "access to their own social APP" line points at: a fire-and-forget action that pushes a message into a Work WeChat (企业微信/WeCom) group chat via its group-bot webhook. Wire your agent's final reply, a "render finished" ping, or an alert into this node's content field and it lands in whatever WeCom group you've configured - the same pattern as a Slack or Discord incoming webhook, just for the platform most Chinese teams actually live in.

It's a genuinely terminal node - is_output_node is true and it has no outputs at all. There's nothing to wire downstream of it; put it at the end of a branch, not in the middle.

Setting it up on the WeCom side

The url field is where a WeCom group's incoming-webhook URL goes. You get that URL by adding a "群机器人" (group bot) to the WeCom group chat you want to notify - WeCom hands you a webhook URL with a key baked into it when you do. Nothing gets sent without a real webhook URL there; the field being optional on the node just means ComfyUI won't block you from leaving it blank, not that the node will do anything useful if you do.

Inputs that matter

• content (default "hello world") - the message body. This is the field you'd typically wire an LLM node's text output into.
• msgtype - an enum, text or markdown (default markdown). WeCom's own webhook API supports a few message types; this node exposes the two you'll actually use for LLM-generated content. Worth knowing: WeCom's markdown rendering is a cut-down subset of the format, not full GitHub-flavored markdown - if a message comes out looking mangled, switching to text is the fastest way to confirm whether it's a formatting problem or a content problem.
• is_enable - the usual boolean kill switch across this pack's nodes.
• url (optional) - the webhook URL described above.

Installing it

Same install as every node in this pack - it's all one repository. ComfyUI Manager: search comfyui_LLM_party, install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/heshengtao/comfyui_LLM_party

then pip install -r requirements.txt inside your ComfyUI Python environment (through python_embeded\python.exe on the portable Windows build), and restart ComfyUI.

Where people get tripped up

Two things worth checking before you assume the node is broken. First, a blank or wrong url fails silently from the workflow's perspective - ComfyUI has no way to know the webhook URL you typed is invalid, so if nothing shows up in the WeCom group, go verify the URL against the one WeCom actually gave you for that bot, not the node's logic. Second, if you're sending anything with headers, bullet points, or bold text and it looks broken in the group chat, that's almost certainly WeCom's restricted markdown subset rather than a bug in this node - try msgtype: text first to isolate whether the content itself is fine.

Beyond that, this is one of the simpler nodes in the pack: three real fields, no model downloads, no heavy dependencies specific to it. If it's not working, the webhook URL is the first and most likely place to look.