Overview
This node listens to various real-time events from a messaging platform (likely Zalo, based on context clues). It enables workflows to react automatically when specific types of events occur, such as receiving messages, group-related events, reactions to messages, or message undo actions. The node is useful for automating responses, logging activities, or triggering other processes based on user or group interactions.
Practical examples include:
- Automatically responding to incoming user or group messages.
- Tracking group membership changes or other group events.
- Monitoring reactions added to messages for sentiment analysis or engagement tracking.
- Detecting when messages are retracted and handling them accordingly.
Properties
| Name | Meaning |
|---|---|
| Events | Select which event types to listen for: - Message: Listen to messages from users or groups. - Group: Listen to group-related events. - Reaction: Listen to message reaction events. - Undo: Listen to message undo (retraction) events. |
| Include Self Events | Boolean flag indicating whether to listen to events sent by the bot itself. |
| Allowed Thread IDs | Comma-separated list of thread IDs (groups or users) to restrict event listening to. If empty, all threads are listened to. |
| Blocked Thread IDs | Comma-separated list of thread IDs to exclude from event listening. If empty, no threads are blocked. |
| Get Metadata | Boolean flag to fetch additional user metadata from the platform (e.g., user profile details). |
Output
The node outputs JSON objects representing the events it listens to. Each output item includes:
json: The event data serialized as JSON, containing details about the event type, content, sender, and timestamp.event: The type of event received (e.g., "message", "group_event", "reaction", "undo").timestamp: The time when the event was received.workflow_id: The ID of the workflow instance processing the event.
If the "Get Metadata" option is enabled, the output also includes enriched user information fetched from the platform.
The node does not output binary data.
Dependencies
- Requires an active connection to the messaging platform's real-time event API.
- Needs appropriate API authentication credentials configured in n8n to access the platform.
- Optionally depends on the platform's user metadata API if "Get Metadata" is enabled.
Troubleshooting
- No events received: Check that the node is properly authenticated and connected to the platform. Verify that the selected event types and thread ID filters match actual events occurring.
- Events missing expected data: If "Get Metadata" is disabled, user details may be limited. Enable this option to enrich event data.
- Permission errors: Ensure the API key or token has sufficient permissions to subscribe to events and fetch metadata.
- Blocked or allowed thread IDs misconfigured: Incorrectly specifying these lists can prevent events from being captured. Use comma-separated numeric IDs without spaces.
- Include Self Events not working as expected: Confirm whether the platform sends self-generated events and how they are filtered.
Links and References
Note: Internal credential names and implementation details have been abstracted to comply with guidelines.