Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node allows users to reply to a specific message within the Feishu messaging platform. It supports replying with various types of content such as text, rich text, images, files, audio, video, stickers, interactive cards, and shared contact cards. This functionality is useful in automating responses in chatbots, customer support workflows, or any scenario where programmatic interaction with Feishu messages is needed.

For example, you can use this node to automatically reply to incoming user messages with predefined answers, send media files as replies, or share contact cards in response to queries.

Properties

Name Meaning
待回复的消息的ID The ID of the message to which you want to reply.
消息类型 The type of the reply message. Options include: 文本 (text), 富文本 (rich text), 图片 (image), 文件 (file), 语音 (audio), 视频 (video), 表情包 (sticker), 卡片 (interactive card), 分享群名片 (share group contact card), 分享个人名片 (share personal contact card).
消息内容 The content of the reply message, provided as a JSON string representing the message structure.
UUID A custom unique string used for deduplication when sending the reply message.
是否以话题形式回复 Whether to reply in a thread form (true/false).

Output

The node outputs an array of JSON objects representing the result of the reply operation for each input item. Each output item corresponds to one reply action and contains the response data from Feishu's API about the sent message.

If the reply includes binary data (e.g., images, files), the node handles it accordingly, but the main output is focused on the JSON response describing the message sent.

Dependencies

  • Requires an API key credential for authenticating with Feishu's API.
  • Needs proper configuration of the Feishu API credentials in n8n.
  • Relies on Feishu's messaging API endpoints to send replies.

Troubleshooting

  • Common issues:

    • Invalid or missing message ID will cause the reply to fail.
    • Incorrectly formatted JSON in the "消息内容" property may lead to errors.
    • Using an unsupported message type or malformed content structure can cause API rejections.
    • Duplicate UUIDs might be ignored by the API if deduplication is triggered.

  • Error messages:

    • Errors related to authentication usually indicate misconfigured or expired API credentials.
    • Validation errors from the API often point to incorrect message IDs or content format.
    • Network or timeout errors suggest connectivity issues with Feishu's servers.

To resolve these:

  • Double-check the message ID and ensure it exists.
  • Validate the JSON structure of the message content before sending.
  • Confirm that the API credentials are correctly set up and have necessary permissions.
  • Use unique UUID values for each reply to avoid unintended deduplication.

Links and References

Discussion