Overview
This node allows you to show a "typing" indicator in Zalo chat threads, signaling that a message is being composed. It supports both individual user chats and group chats. This feature is useful for enhancing real-time communication experiences by letting recipients know when someone is actively typing a message.
Practical examples:
- In a customer support workflow, showing typing status can reassure customers that their query is being addressed.
- In team collaboration tools, indicating typing status helps coordinate conversations more smoothly.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the Zalo thread where the typing indicator will be shown. |
| Type | The type of the thread: either "User" (individual chat) or "Group" (group chat). |
Output
The node outputs an array of JSON objects, each corresponding to an input item processed. Each output object has the following structure:
{
"success": true,
"message": "OK"
}
success: A boolean indicating whether the typing event was sent successfully.message: A string confirming the operation status ("OK" on success).
If an error occurs and the node is configured to continue on failure, the output for that item will include:
{
"success": false,
"error": "Error message describing what went wrong"
}
The node does not output any binary data.
Dependencies
- Requires an API key credential with access to the Zalo API.
- Uses the Zalo API client library to send typing events.
- Requires proper configuration of credentials including cookie, device IMEI, and user agent strings for authentication.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause login failures.
- Incorrect Thread ID or Type may prevent sending the typing event.
- Network connectivity problems can interrupt API calls.
Error messages:
"Failed to initialize Zalo API. Check your credentials."
Indicates that the node could not authenticate with Zalo. Verify the API credentials and ensure they are valid."Zalo login error: <details>"
Shows detailed login failure reasons. Check the provided cookie, IMEI, and user agent values."Cannot send typing event: <details>"
Occurs if sending the typing event fails for a specific thread. Confirm the thread ID and type are correct."Error sending Zalo message:"
General error during message sending; inspect logs for details.
To resolve errors, verify all input parameters, ensure credentials are up to date, and check network connectivity.