Mtai Zalo Message Trigger icon

Mtai Zalo Message Trigger

Sự kiện lắng nghe tin nhắn trên Zalo

Overview

This node listens for incoming messages on the Zalo platform, a popular messaging app. It acts as a trigger that activates workflows when new messages arrive either from individual users or groups. This is useful for automating responses, logging conversations, or integrating Zalo messages with other systems.

Common scenarios include:

  • Automatically processing user inquiries received via Zalo.
  • Monitoring group chats for specific keywords or events.
  • Triggering notifications or actions based on message content.

For example, a business could use this node to listen for customer messages and automatically create support tickets or send acknowledgments.

Properties

Name Meaning
Event Types Types of messages to listen for. Options: User Messages (messages from individual users), Group Messages (messages from groups). Multiple selections allowed.
Self Listen Whether to allow listening to messages sent by yourself. Boolean value: true or false.

Output

The node outputs JSON data representing the incoming message event. The output structure contains a message object with details about the received message from Zalo.

Example output JSON structure:

{
  "message": {
    // message details as received from Zalo API
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential to connect to the Zalo platform.
  • Uses the zca-js library to handle Zalo API interactions and message listening.
  • Needs proper configuration of webhook URL in n8n to receive incoming message events.
  • Requires valid Zalo credentials including cookie, IMEI, and user agent information.

Troubleshooting

  • Connection failures: If the node throws "Zalo connection failed," verify that the provided credentials are correct and have not expired.
  • No messages received: Ensure the webhook URL is correctly set up and publicly accessible. Also, confirm that the selected event types match the incoming message types.
  • Self Listen issues: If you do not receive messages sent by yourself, check the "Self Listen" property is enabled if that behavior is desired.
  • Credential errors: Make sure the API key credential includes all necessary authentication details such as cookies and device identifiers.

Links and References

Discussion