Zalo Message Trigger icon

Zalo Message Trigger

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

Overview

This node acts as a trigger that listens for incoming messages on the Zalo platform, a popular messaging app. It is designed to capture real-time message events either from individual users or group chats, depending on configuration. This node is useful in scenarios where you want to automate workflows based on new messages received on Zalo, such as customer support automation, chatbots, or notification systems.

For example, you could use this node to:

  • Trigger a workflow whenever a user sends a message to your Zalo account.
  • Listen to group chat messages and process them for sentiment analysis or keyword detection.
  • Automatically respond to messages or log conversations for analytics.

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 message event received from Zalo. The output structure contains the full message object under the json field, which includes all details about the message event captured by the webhook.

If the node receives a message event, it returns an array with one element containing the message data, e.g.:

[
  {
    "message": {
      // full message object from Zalo
    }
  }
]

There is no indication that the node outputs binary data.

Dependencies

  • Requires valid Zalo API credentials configured in n8n to authenticate and connect to the Zalo service.
  • Uses an external Zalo SDK/library (zca-js) to handle connection and message listening.
  • Needs a webhook URL configured in n8n to receive incoming message events from Zalo.

Troubleshooting

  • Connection failures: If the node throws "Zalo connection failed," verify that the provided Zalo API credentials are correct and have not expired.
  • No credentials found: Ensure that the required API key or authentication token is properly set up in n8n credentials.
  • Webhook issues: Make sure the webhook URL is accessible from the internet and correctly registered with Zalo to receive events.
  • Listening to self messages: If you do not receive messages sent by yourself, check the "Self Listen" property; it must be enabled to capture those messages.
  • Event types filtering: If no messages are triggering the workflow, confirm that the selected event types match the actual message sources (user vs group).

Links and References

Discussion