Actions25
Overview
This node integrates with Wechat Work to perform various operations related to messaging and other resources. Specifically, the "撤回消息" (Recall Message) operation under the "消息推送" (Message Push) resource allows users to recall or retract a previously sent message by providing its unique message ID. This is useful in scenarios where a message was sent by mistake or needs to be withdrawn for any reason.
Practical examples include:
- Automatically recalling messages that contain sensitive or incorrect information.
- Allowing users to manually trigger message recalls from within an automation workflow.
- Managing message lifecycle in customer support or internal communication systems.
Properties
| Name | Meaning |
|---|---|
| *消息ID | The unique message ID obtained from the message sending interface; identifies the message to recall. |
Output
The node outputs JSON data representing the result of the recall operation. Typically, this will include confirmation of success or details about any error encountered during the recall process.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message for the failed item.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Wechat Work API.
- Needs network access to the Wechat Work API endpoints.
- The node depends on internal helper modules for resource and operation management.
- Proper configuration of credentials including base URL, corporate ID, and secret is necessary.
Troubleshooting
Common issues:
- Invalid or expired API credentials leading to authentication failures.
- Providing an incorrect or non-existent message ID will cause the recall operation to fail.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors thrown during execution will include the message describing the failure.
- If "Continue On Fail" is disabled, the node will stop execution on the first error.
- To resolve errors, verify credentials, ensure the message ID is correct, and check network connectivity.