PopoOpenPlatformOA Api icon

PopoOpenPlatformOA Api

POPO OpenPlatform OA API

Actions12

消息 → 发送消息

AI-generated

Overview

This node interacts with the POPO OpenPlatform OA API to perform various operations related to messages, menus, users, and groups. Specifically, for the '消息' (message) resource and '发送消息' (send message) operation, it sends custom or template messages, recalls messages, or downloads message files by making API requests with the provided request body or file ID. This node is useful for automating message sending, recalling, and file downloading in workflows that integrate with the POPO OpenPlatform OA system.

Use Case Examples

  1. Sending a custom text message to a user by specifying the message body in JSON format.
  2. Sending a template message using predefined templates with dynamic content.
  3. Recalling a previously sent message by providing its message ID.
  4. Downloading a file attached to a message by specifying the file ID.

Properties

Name Meaning
文件ID The file ID to download, required for downloading message files.
文件消息ID The message ID to recall, used when recalling a message.
Body The JSON body of the request to send, containing message details such as recipient, message type, and content. Required for sending custom or template messages and recalling messages.

Output

JSON

  • touser - The recipient user ID of the message.
  • msgtype - The type of the message being sent (e.g., text).
  • text
    • content - The content of the text message.
  • fileId - The ID of the file to download when downloading message files.
  • msgId - The ID of the message to recall when recalling messages.

Dependencies

  • An API key credential for authenticating with the POPO OpenPlatform OA API.

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to perform message operations.
  • Verify that the fileId and msgId parameters are correctly provided when downloading files or recalling messages, respectively.
  • Check the JSON structure of the 'Body' parameter to ensure it matches the expected format required by the API.
  • Common error messages may include authentication failures, invalid message IDs, or malformed request bodies. Resolving these typically involves verifying credentials, input parameters, and JSON formatting.

Links

Discussion