Zalo User Interact

Overview

This node is designed to send a sticker message to a Zalo user or group chat. It allows users to specify the recipient by their User/Group ID and select a sticker to send based on keywords. This functionality is useful for automating interactions in Zalo conversations, such as sending predefined stickers in response to certain triggers or events.

Common scenarios:

• Sending a fun or expressive sticker automatically when a specific event occurs (e.g., a new order, support ticket update).
• Engaging users in a group chat with relevant stickers without manual intervention.
• Enhancing chatbot responses by including stickers that match the conversation context.

Practical example:

• When a customer places an order, the node sends a "thank you" sticker identified by the keyword "cute" to the customer's Zalo user ID.
• In a team group chat, the node sends a "funny" sticker to lighten the mood after a meeting summary is posted.

Properties

Output

The node outputs a JSON array where each element corresponds to the result of sending a sticker message for each input item. Each element contains at least:

• A success flag indicating if the message was sent successfully.
• Additional metadata or error information if applicable.

The output does not include binary data; it focuses on the status and details of the sent sticker messages.

Dependencies

• Requires an active connection to the Zalo messaging platform.
• Needs valid API credentials (an API key or authentication token) configured in n8n to authorize requests to Zalo's messaging API.
• The node internally uses helper classes and methods to handle API communication, message formatting, and error handling.

Troubleshooting

Common issues:

• Invalid User/Group ID: If the provided threadId is incorrect or does not exist, the API call will fail. Verify the ID before running the node.
• Incorrect Thread Type: Sending a sticker to a user while specifying the thread type as group (or vice versa) may cause errors.
• Sticker Keyword Not Found: If the keyword does not match any available sticker, the message cannot be sent.
• Authentication Errors: Missing or invalid API credentials will prevent the node from sending messages.
• API Rate Limits: Excessive requests might trigger rate limiting by Zalo's API.

Error messages and resolutions:

• "Failed to send message": Check the threadId and threadType values, ensure the API credentials are correct.
• "Sticker not found": Confirm that the stickerKeywords value matches a valid sticker keyword supported by Zalo.
• "Unauthorized": Reconfigure the API credentials in n8n.
• Timeout or network errors: Ensure stable internet connectivity and that Zalo's API endpoints are reachable.

Links and References

• Zalo Official API Documentation
• Zalo Messaging API Guide
• n8n community forums and documentation for custom node development and troubleshooting.

Note: The above summary is based solely on static analysis of the provided source code and property definitions, without executing or dynamically resolving code.