Zalo Message Trigger
AI-generatedOverview
The Zalo Message Trigger node listens for incoming messages on the Zalo platform, supporting both user messages and group messages. It is useful for automating workflows that need to react to real-time Zalo messages, such as customer support bots, notification systems, or message logging. The node can be configured to listen to specific types of messages and optionally include messages sent by the user themselves.
Use Case Examples
- A business wants to automate responses to customer inquiries received via Zalo user messages.
- A group admin wants to monitor and log all messages sent in a Zalo group chat for compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Event Types | Specifies the types of Zalo messages to listen for, either user messages, group messages, or both. |
| Self Listen | Determines whether the node should also listen to messages sent by the user themselves. |
Output
JSON
message- The incoming Zalo message data received from the webhook.
Dependencies
- Requires Zalo API credentials including cookie, IMEI, and user agent for authentication.
Troubleshooting
- Common issues include invalid or expired Zalo API credentials, which will cause connection failures.
- If the node throws 'No API instance found' error, verify that the credentials are correctly provided and valid.
- Webhook URL must be accessible and correctly configured to receive POST requests from Zalo message events.