Actions2
- Zalo Send Message Actions
Overview
This node allows sending message status updates (such as typing indicators) to a Zalo chat thread, either with an individual user or a group. It is useful in scenarios where you want to programmatically indicate that a user or bot is typing or update the message status in a conversation on the Zalo platform.
Practical examples include:
- Showing a "typing..." indicator in a Zalo chat while your bot processes a response.
- Sending custom message status updates to inform users about ongoing actions.
- Integrating Zalo messaging status updates into automated workflows for customer support or marketing.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the Zalo chat thread where the message status will be sent. |
| Type | The type of the message recipient: either a single User (0) or a Group (1). |
Output
The node outputs JSON data with the following structure:
success: Boolean indicating if the operation was successful.message: A simple confirmation string"OK"when sending status updates succeeds.- In case of errors,
errorcontains the error message. - Additional fields may include details about the thread and message content depending on the exact operation.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Zalo platform.
- Uses the
zca-jslibrary internally to interact with Zalo's API. - Needs proper configuration of credentials within n8n to function correctly.
Troubleshooting
Common issues:
- Failure to initialize the Zalo API usually indicates invalid or missing credentials.
- Errors sending typing events might occur if the thread ID or type is incorrect.
- Network or permission issues can cause message sending failures.
Error messages:
"Failed to initialize Zalo API. Check your credentials."— Verify that the API key and other authentication details are correct."Error sending Zalo message: <details>"— Indicates a problem during the send operation; check thread ID, message type, and network connectivity.- If the node throws errors referencing inability to send typing events, ensure the thread exists and the bot/user has permission to send status updates.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation on Creating Custom Nodes
- zca-js GitHub Repository (for the underlying Zalo API client used)