Zalo Send Message icon

Zalo Send Message

Gửi tin nhắn qua API Zalo sử dụng kết nối đăng nhập bằng cookie

Actions4

Overview

This node allows sending message status updates through the Zalo messaging platform. Specifically, the "Gửi trạng thái tin nhắn" (Send message status) operation lets users send typing indicators or other status signals to a specified chat thread on Zalo. This is useful for automating interactions where you want to simulate user activity, such as showing that a message is being typed or updating the status of a conversation.

Practical examples include:

  • Indicating to a recipient that a reply is being composed.
  • Sending read receipts or other custom status updates in group or individual chats.
  • Automating chatbots to provide more natural conversational feedback.

Properties

Name Meaning
Thread ID The unique identifier of the chat thread where the message status will be sent.
Type The type of the message thread: 0 for User (individual chat), 1 for Group chat.

Output

The node outputs a JSON object with the following structure:

  • success: Boolean indicating if the operation was successful.
  • response: The raw response from the Zalo API after sending the status update.
  • threadId: The ID of the thread where the status was sent.
  • threadType: The type of the thread (User or Group).
  • messageContent: Contains details about the message or status sent.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Zalo API using appropriate authentication credentials (an API key or token).
  • The node internally uses a Zalo API client library to handle communication.
  • Requires proper configuration of credentials within n8n to authenticate requests.
  • Uses file system utilities and helper functions for media handling in other operations, but not specifically for this one.

Troubleshooting

  • Common issues:

    • Failure to initialize the Zalo API client due to missing or invalid credentials.
    • Invalid or missing Thread ID causing the API call to fail.
    • Incorrect Type value leading to unexpected behavior (should be 0 or 1).
    • Network or API errors when communicating with Zalo servers.

  • Error messages:

    • "Zalo API not initialized": Indicates missing or invalid API credentials; verify credential setup.
    • "Cannot send typing event": Occurs if the typing status cannot be sent; may be transient or due to incorrect thread info.
    • NodeOperationError with detailed messages usually indicate parameter issues or API failures; check input parameters and network connectivity.

  • Resolution tips:

    • Ensure the API credentials are correctly configured and valid.
    • Double-check the Thread ID and Type inputs.
    • Review network access and firewall settings.
    • Enable node logging to get detailed error information.

Links and References

Discussion