PopoOpenPlatformOA Api

Overview

The "撤回消息" (Recall Message) operation under the "消息" (Message) resource in this custom n8n node allows users to recall or withdraw a previously sent message via the POPO OpenPlatform OA API. This is useful in scenarios where a message was sent in error, contains incorrect information, or needs to be removed for compliance reasons.

Practical examples:

• Automatically retracting messages that contain sensitive data.
• Withdrawing notifications that were sent to the wrong recipients.
• Implementing workflows where messages are recalled after a certain condition is met.

Properties

Note: For the "撤回消息" operation, the most relevant properties are "文件消息ID" (message ID to recall) and "Body" (request payload). "文件ID" is not typically used for recalling messages.

Output

The output will be a JSON object (or array of objects) representing the response from the POPO OpenPlatform OA API after attempting to recall the message. The exact structure depends on the API's response, but it generally includes status codes, messages, and possibly details about the recalled message.

Example output structure:

[
  {
    "errcode": 0,
    "errmsg": "ok",
    "recall_status": "success"
  }
]

(This is an illustrative example; actual fields may vary based on the API response.)

Dependencies

• External Service: Requires access to the POPO OpenPlatform OA API.
• API Credentials: You must configure the popoOpenPlatformOAApi credentials in n8n.
• Environment: No special environment variables are mentioned, but network access to the POPO API endpoint is necessary.

Troubleshooting

Common issues:

• Invalid or missing credentials: Ensure the correct API key/token is set up in n8n credentials.
• Incorrect message ID: If the provided "文件消息ID" does not correspond to an existing or recallable message, the API may return an error.
• Malformed Body: If the "Body" property is not valid JSON or lacks required fields, the API may reject the request.

Possible error messages:

• "errcode": 40001, "errmsg": "invalid credential"
  Resolution: Check your API credentials.
• "errcode": 40003, "errmsg": "invalid message id"
  Resolution: Verify the message ID you are trying to recall.
• "errcode": 40035, "errmsg": "invalid parameter"
  Resolution: Ensure all required parameters are correctly filled and formatted.

Links and References

• POPO OpenPlatform OA API Documentation (if available)
• n8n Documentation: Custom Nodes
• n8n Credentials Setup

Summary:
This node operation enables automated message recall in POPO OA workflows, supporting robust error handling and integration with other n8n processes. Proper configuration of input properties and credentials is essential for successful execution.