Actions25
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node allows sending a sticker message to a specified Zalo user or group chat. It is useful in scenarios where you want to automate the sending of expressive sticker content within conversations on the Zalo platform, such as for marketing campaigns, customer engagement, or interactive bots.
For example, you can use this node to send a "funny" or "cute" sticker to a user or group when a certain event occurs, like welcoming new members or responding to specific triggers.
Properties
| Name | Meaning |
|---|---|
| User/Group Id | The ID of the Zalo user or group chat to which the sticker message will be sent. |
| Thread Type | The type of conversation: either a User (0) or a Group (1). |
| Sticker Keywords | Keywords describing the sticker to send, e.g., "cute", "funny". This selects the sticker. |
Output
The node outputs an array of JSON objects representing the results of sending the sticker messages. Each object contains at least:
json: The JSON response from the Zalo API indicating success or failure of the send operation.- If applicable, additional metadata about the message or any errors encountered.
The node does not output binary data.
Dependencies
- Requires an active connection to the Zalo messaging platform via an API key or authentication token configured in n8n credentials.
- Uses internal helper libraries for HTTP requests and data handling.
- No external dependencies beyond standard Node.js modules and n8n framework utilities.
Troubleshooting
- Invalid User/Group ID: If the provided thread ID is incorrect or does not exist, the node will fail to send the message. Verify the ID is correct.
- Incorrect Thread Type: Ensure that the thread type matches the ID type (User vs Group).
- Sticker Keyword Not Found: If the keyword does not match any available stickers, the API may return an error or no message will be sent.
- Authentication Errors: Make sure the API key or authentication token is valid and has permissions to send messages.
- API Rate Limits: Sending too many messages in a short time may trigger rate limits; handle retries accordingly.
- Error Messages: The node logs errors with details including error message and stack trace. Review these logs to diagnose issues.
Links and References
Note: The above summary is based on static analysis of the provided source code and property definitions without executing the code. Internal credential names and sensitive identifiers have been generalized.