Actions12
Zalo User → Thu Hồi Tin Nhắn
AI-generatedOverview
This node operation "Thu Hồi Tin Nhắn" (Undo Message) for the resource "Zalo User" allows users to revoke or undo a previously sent message in a Zalo chat thread. It is useful when you want to delete or retract a message that was mistakenly sent or needs to be removed from the conversation.
Typical use cases include:
- Automatically removing sensitive or incorrect messages after sending.
- Managing chat content programmatically by revoking messages based on certain conditions.
- Moderation tools that allow admins to undo inappropriate messages.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the user or chat thread where the message was sent. |
| Thread Type | The type/category of the user or thread (e.g., individual, group). |
| msgId | The unique identifier of the message to be undone (revoked). |
| cliMsgId | The client-side message ID associated with the message to be undone. |
Output
The output JSON contains at least two fields:
status: A string indicating the status of the undo operation (e.g., success or failure).response: The detailed response from the underlying API call that performs the message revocation.
The output is paired with the input item index to maintain correspondence between inputs and outputs.
No binary data output is indicated.
Dependencies
- Requires an API authentication token or cookie credentials to interact with the Zalo service.
- Uses an internal class instance (likely a Zalo API client) initialized with authentication cookies, IMEI, and user agent strings.
- The node depends on external modules for HTTP requests and error handling.
- Proper configuration of credentials containing necessary authentication details is mandatory.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens/cookies will cause the operation to fail.
- Incorrect or missing message IDs (
msgIdorcliMsgId) will result in errors or no action. - Network connectivity problems can prevent communication with the Zalo API.
Error messages:
- Errors thrown if the API client is not properly initialized, often due to missing or invalid credentials.
- Specific error responses from the Zalo API are passed through in the
responsefield; inspecting these helps diagnose issues.
Resolutions:
- Ensure valid and up-to-date authentication credentials are provided.
- Verify that the message IDs correspond to actual messages in the specified thread.
- Check network access and API endpoint availability.
Links and References
- Zalo Official API Documentation (for reference on message operations)
- n8n documentation on creating custom nodes and handling credentials: https://docs.n8n.io/
Note: The source code was obfuscated, but key logic and property usage were extracted via static analysis without runtime execution.