Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node allows sending messages through the Feishu platform by specifying the recipient and message details. It supports various user identification types and multiple message formats, making it versatile for different communication needs within Feishu.

Common scenarios include:

  • Sending notifications or alerts to specific users or groups.
  • Sharing files, images, or rich content in chats.
  • Automating message delivery based on external triggers or workflows.

Practical example:

  • Automatically send a text message to a user identified by their Open ID when a new support ticket is created.
  • Share an image or file with a team chat using the Chat ID after a project milestone is reached.

Properties

Name Meaning
用户ID类型 The type of identifier used for the message recipient. Options: Open ID (user identity within an app), Union ID (user identity across apps under the same developer), User ID (user identity within a tenant), Email, Chat ID (group chat).
消息接收者的 ID The actual ID of the message recipient, matching the selected 用户ID类型. For example, if 用户ID类型 is "Open ID", this should be the user's Open ID string.
消息类型 The format/type of the message being sent. Options include: text, rich text (post), image, file, audio, video, sticker, interactive card, share group card, share personal card, system message.
消息内容 The content of the message as a JSON string. The structure depends on the 消息类型 chosen. For example, for text messages, it might be {"text":"your message"}.
UUID A custom unique string used for deduplication when sending messages. If provided, it helps prevent sending duplicate messages.

Output

The node outputs an array of JSON objects representing the result of each message send operation. Each output item corresponds to an input item processed and contains the response data from the Feishu API call.

If errors occur and "continue on fail" is enabled, error information will be included in the output JSON for the failed items.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Feishu platform.
  • The node uses internal helper methods to build and send requests to Feishu's messaging API.
  • No additional external dependencies are specified beyond the Feishu API access.

Troubleshooting

  • Common issues:

    • Incorrect or missing recipient ID or ID type can cause message sending failures.
    • Malformed JSON in the 消息内容 property may lead to errors.
    • Using an invalid or expired API key credential will prevent successful API calls.

  • Error messages:

    • Errors thrown during execution include detailed messages and stack traces logged internally.
    • If "continue on fail" is disabled, the node will stop on the first error.
    • To resolve errors, verify all input parameters, ensure valid authentication, and check the message content format against Feishu's API requirements.

Links and References

Discussion