Zalo Event Trigger icon

Zalo Event Trigger

Nhận event từ Zalo (Cá nhân)

Overview

This node listens for various event types from the Zalo platform, such as messages, group events, reactions, and message retractions. It allows users to specify which events to listen for, whether to include events sent by themselves, and to filter events by allowed or blocked group/user IDs. Additionally, it can fetch extra user metadata from Zalo. This node is useful for automating workflows based on real-time Zalo interactions, such as responding to messages, monitoring group activities, or tracking reactions.

Use Case Examples

  1. Automatically respond to incoming messages from specific groups or users.
  2. Trigger workflows when a message reaction is added or removed.
  3. Log message retraction events for audit purposes.
  4. Fetch detailed user information when a message event occurs.

Properties

Name Meaning
Events Select the types of Zalo events to listen for, including messages, group events, reactions, and undo (message retraction) events.
Event Từ Bạn Boolean flag to include or exclude events sent by yourself.
ID Nhóm/user Nhận Event Comma-separated list of group or user IDs from which to receive events. If empty, events from all groups/users are received.
ID Nhóm/user Không Nhận Event Comma-separated list of group or user IDs from which to block events. If empty, no groups/users are blocked.
Lấy Thông Tin Người Dùng Boolean flag to fetch additional user metadata from Zalo.

Output

JSON

  • json - The event data received from Zalo, including event type, user info, and metadata if requested.
  • event - The type of event received (e.g., message, group_event, reaction, undo).
  • timestamp - The timestamp when the event was received.
  • workflow_id - The ID of the workflow that processed the event.

Dependencies

  • Requires connection to Zalo API and an API authentication token or key to listen for events and fetch user metadata.

Troubleshooting

  • Ensure the API credentials for Zalo are correctly configured and valid.
  • Verify that the allowedThreadIds and blockedThreadIds are correctly formatted and correspond to valid group or user IDs.
  • If no events are received, check network connectivity and Zalo API status.
  • If user metadata fetching is enabled but fails, verify API permissions and rate limits.

Discussion