Feishu Download Image🐶

Same idea as this pack's Feishu Download Audio node, for pictures instead of voice messages. When someone shares an image with a Feishu bot, what comes back through Feishu's API is a reference, not the file - this node resolves that reference into an actual local image you can feed into a vision LLM, OCR, or any other image-consuming step in your workflow.

What it does

app_id/app_secret are your registered Feishu app's credentials - same authenticated pull pattern as the rest of this pack's Feishu bot nodes, not a public link fetch. message_id is which message the image arrived on, and file_key is the specific attachment within it; Feishu keys media by attachment rather than assuming one image per message. Both fields most naturally come from this pack's FeishuGetHistory node, whose output_is_image output is the signal that a given message actually has an image worth downloading.

Two outputs: image_path, the local path to the downloaded file, and show_help, the usage-reference text this pack attaches across its Feishu and Gitee node family.

Where it fits

This is the "handle image input" branch of the standard Feishu-bot pattern this pack's App Link nodes form together: FeishuGetHistory polls and flags what kind of message came in, this node pulls the image when the flag says there is one, an LLM or vision model does something with it, and FeishuSendMsg sends a reply. If your bot never receives images, you never need this node - it's a conditional branch, not a step every Feishu workflow requires.

Installing it

Standard pack install:

• 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.

Your Feishu app also needs message-attachment read permission granted in the Feishu Open Platform console - a separate scope from basic messaging permissions, and a common thing to have missed when a bot is first set up.

Common issues & troubleshooting

Auth or permission error on download. Confirm the app's Feishu-console scopes actually include reading message resources, not just sending/receiving messages - those are commonly granted separately and it's easy to have one without the other on a freshly registered app.

file_key doesn't resolve. It's only valid paired with the exact message_id it came from - grabbing a file_key from one message and a message_id from another (say, from two different FeishuGetHistory outputs) won't work, since Feishu scopes attachment keys to the message they belong to.

Image downloads but a downstream node rejects it. Check the format actually downloaded - chat apps sometimes deliver images in formats or color modes that not every downstream ComfyUI node handles identically. If the path in image_path is valid and the file opens fine in a normal image viewer, the download itself worked; the mismatch is further down your graph.