Zalo User Trigger icon

Zalo User Trigger

Receive events from Zalo User and trigger workflows

Overview

This n8n custom node is designed to listen for specific types of events and output structured information when those events occur. The node allows users to select which event types they want to monitor, such as messages, group events, reactions, or message undo actions. When an event is detected, the node outputs a JSON object containing details about the event, including its type, timestamp, and the workflow ID.

Common Scenarios:

  • Monitoring chat platforms for new messages or group activities.
  • Triggering workflows in response to user reactions or message deletions.
  • Building automation that responds to real-time communication events.

Practical Examples:

  • Automatically logging all group join/leave events in a chat application.
  • Starting a moderation workflow when a message is deleted (undo event).
  • Notifying a team when someone reacts to a critical announcement.

Properties

Display Name Type Required Description Options
Events multiOptions Yes Chọn các sự kiện mà bạn muốn lắng nghe:
  • Message: Lắng nghe tin nhắn từ người dùng / nhóm
  • Group: Lắng nghe các sự kiện của nhóm
  • Reaction: Lắng nghe sự kiện thả cảm xúc tin nhắn
  • Undo: Lắng nghe sự kiện thu hồi tin nhắn
 - Message
- Group
- Reaction
- Undo

Option Details:

  • Message: Listen for messages from users or groups.
  • Group: Listen for group-related events.
  • Reaction: Listen for message reaction events.
  • Undo: Listen for message recall (undo) events.

Output

The node outputs an array of items, each with the following structure in the json field:

{
  "json": { /* Event-specific data, typically the raw event payload */ },
  "event": "<event_type>",        // One of: "message", "group_event", "reaction", "undo"
  "timestamp": "<ISO8601 string>",// Timestamp when the event was received
  "workflow_id": "<string>"       // The ID of the current n8n workflow
}
  • json: Contains the event's payload, often as a JSON-parsed object or stringified version of the original event.
  • event: Indicates the type of event that triggered the node.
  • timestamp: The exact time the event was processed.
  • workflow_id: The unique identifier of the workflow instance handling the event.

Note: If the node supports binary data, it is not explicitly handled here; the focus is on structured event data.

Dependencies

  • External Services: The node may require integration with external messaging or chat platforms, depending on the events being listened to.
  • API Keys / Auth: If connecting to third-party services, appropriate API credentials must be configured in n8n.
  • n8n Configuration: Ensure the node is properly installed and any required credentials are set up in the n8n instance.

Troubleshooting

Common Issues:

  • No Events Received: Ensure the correct event types are selected in the "Events" property and that the external service is properly connected.
  • Authentication Errors: Missing or invalid API keys can prevent event delivery.
  • Malformed Output: If the event payload is not valid JSON, the output may be empty or cause downstream errors.

Error Messages & Resolutions:

  • Missing Required Property: If "Events" is not selected, the node will not function. Always select at least one event type.
  • Connection Errors: Check network connectivity and credentials for any integrated external services.
  • Unexpected Output Structure: Verify the upstream event source is sending data in the expected format.

Links and References

Discussion