Feishu Bot Send Message🐶

If the plain feishu node is the quick webhook alert, this is the real bot. It trades the one-field key_word setup for a proper Feishu app (app_id + app_secret from the Feishu Open Platform developer console) and gets a lot more capability in return: four message types instead of two, and the ability to target either a group or a specific individual, not just whichever group has your webhook installed.

What it does

msg_type picks the format - text, markdown, image, or audio. text carries the message content (default: a canned "Hello. I am an AI from LLM_Party." - replace it). chat_type picks the destination shape: group (posts into a group chat, addressed by chat_id) or single (a direct message, addressed by user_id or open_id - Feishu's two different ways of identifying an individual user depending on how your app is scoped). Optional file_path is where you point a local image or audio file when msg_type needs one - the field's own default text spells out exactly what it expects: "only image path or audio path."

Two outputs beyond the usual help text: file_key and msg_id. file_key matters if you sent media - it's the reference Feishu assigned to whatever you uploaded via file_path, and holding onto it means you can reuse the same asset in a later message without re-uploading it. msg_id identifies the message itself, useful if a later step in your workflow needs to reference or react to what was just sent.

Where it fits

This is the send half of a complete Feishu bot pipeline this pack's App Link nodes are built to form together: FeishuGetHistory polls a chat for new messages and tells you what kind of content came in, the Feishu download nodes pull any attachment, your LLM logic in between decides what to do with it, and this node sends the reply back - text, a formatted markdown response, or generated media. The simple feishu webhook node covers a much narrower slice of this (one-way group alerts); this is what you reach for once you're actually building a bot that holds a conversation.

Installing it

Standard pack install, no extra step for this node:

• ComfyUI Manager: search "comfyui_LLM_party", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/heshengtao/comfyui_LLM_party, then pip install -r requirements.txt from inside the pack folder using ComfyUI's Python, then restart.

The Feishu-side setup is separate and mandatory before this node can do anything: register an app in the Feishu Open Platform console, enable its bot capability, grant it message-sending permissions, and get it added to whatever group or scoped to whatever user you're targeting. app_id/app_secret come from that registration.

Common issues & troubleshooting

Auth errors, nothing sends. Almost always app_id/app_secret being wrong, expired, or belonging to an app that hasn't had the right messaging permission/scope granted in the Feishu developer console - this is a proper API credential, not a copy-paste webhook token, and Feishu's permission model is stricter about what a given app is actually allowed to do.

chat_type is single but the message doesn't land. Double check you're using the identifier Feishu's API actually expects for the target user in your app's context - user_id and open_id are two different identifier spaces Feishu maintains for the same person, and mixing them up is a common source of "valid-looking id, message goes nowhere."

Sent an image/audio message and it fails, but text works fine. Confirm file_path points at a file that genuinely exists and is readable from wherever ComfyUI's process is running, not just a path that looks right - media messages have an upload step behind the scenes that a bad path fails silently on more often than a malformed text send does.