Actions2
- Zalo Send Message Actions
Overview
This node allows sending a "typing status" event in Zalo chat threads via the Zalo API. It is useful for indicating to other participants that you are currently typing a message, enhancing real-time communication experience in both one-on-one and group conversations.
Typical use cases include:
- Showing typing indicators in customer support chatbots integrated with Zalo.
- Notifying users in group chats that a message is being composed.
- Enhancing interactive messaging workflows where user presence or activity feedback is important.
For example, before sending an actual message, this node can be used to trigger the typing indicator in a specific thread, making the conversation feel more natural and responsive.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the Zalo chat thread where the typing status will be sent. |
| Type | The type of the thread: either "User" (individual chat) or "Group" (group chat). Options: User, Group |
Output
The node outputs JSON data with the following structure:
success: Boolean indicating if the typing status was sent successfully.message: A simple confirmation string"OK"when successful.- In case of failure (if continueOnFail is enabled), it outputs:
success: falseerror: Error message describing what went wrong.
No binary data output is produced by this operation.
Example output on success:
{
"success": true,
"message": "OK"
}
Dependencies
- Requires valid Zalo API credentials including a cookie, device IMEI, and user agent string.
- The node uses an external Zalo API client library to interact with Zalo services.
- Proper configuration of these credentials in n8n is mandatory for the node to function.
- No additional environment variables are explicitly required beyond the credential setup.
Troubleshooting
Common issues:
- Invalid or expired Zalo API credentials will cause initialization failure.
- Incorrect Thread ID or Type may result in failure to send the typing event.
- Network connectivity problems can prevent communication with Zalo servers.
Error messages:
"Failed to initialize Zalo API. Check your credentials."
Means the node could not authenticate with Zalo. Verify the API credentials and their validity."Zalo login error: <details>"
Indicates an error during the login process to Zalo API. Check the cookie, IMEI, and user agent values."Zalo API not initialized"
The node attempted to send a typing event without a successful API login. Ensure credentials are correct and the login step succeeds."Cannot send typing event"
The typing event failed to send, possibly due to invalid parameters or network issues.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings.
Links and References
- Zalo Official Developer Documentation
- Zalo Messaging API Overview
- n8n Documentation on Creating Custom Nodes