Zalo Message Trigger icon

Zalo Message Trigger

Lắng nghe các sự kiện trên Zalo

Zalo Message Trigger

AI-generated

Overview

This node listens for various event types on the Zalo platform, such as new messages, message undo, reactions, typing notifications, group events, friend events, message seen/delivered statuses, reminders, and polls. It is useful for automating workflows based on real-time Zalo interactions, for example, triggering actions when a new message arrives or when a user reacts to a message.

Use Case Examples

  1. Trigger a workflow when a new message or reaction is received in a Zalo chat.
  2. Listen for group events like members joining or leaving to update group management systems.
  3. Automate reminders or poll responses based on Zalo events.

Properties

Name Meaning
Events The types of Zalo events to listen for, such as messages, reactions, typing, group events, friend events, reminders, and polls.
Self Listen Whether to listen to events generated by the user themselves.
Thread Type Filter Filter events by thread type: all, user-only, or group-only.
Auto Reconnect Settings Settings for automatic reconnection including max retry count and retry interval in seconds.
Allowed Thread IDs Comma-separated list of thread IDs to listen to. If empty, listens to all threads.
Blocked Thread IDs Comma-separated list of thread IDs to ignore.

Output

JSON

  • eventName - The name of the event received from Zalo.
  • data - The event data payload containing details specific to the event type.
  • reminderInfo
    • type - For reminder events, the type of reminder.
    • action - For reminder events, the action performed.
    • timestamp - For reminder events, the timestamp of the event.
  • pollInfo
    • pollId - For poll events, the poll identifier.
    • action - For poll events, the action performed on the poll.

Dependencies

  • Zalo API credentials (cookie, IMEI, user agent) required for authentication and event listening.

Troubleshooting

  • Connection failures due to invalid or expired Zalo API credentials. Ensure credentials are correct and up to date.
  • Max retry count reached on connection loss. Adjust retry settings or check network stability.
  • Events not triggering due to thread ID filters. Verify allowed and blocked thread ID lists.
  • Errors in webhook delivery. Ensure the webhook URL is accessible and correctly configured.

Discussion