Zalo Trigger icon

Zalo Trigger

Zalo Trigger
Join our community

Overview

This node listens for incoming messages and triggers workflows when new messages arrive. It supports filtering messages by type (private or group) and by thread ID, allowing users to react only to specific conversations or message categories.

Common scenarios where this node is beneficial include:

  • Automating responses to private messages from customers.
  • Monitoring group chats for certain keywords or events.
  • Filtering messages within a particular thread to trigger follow-up actions.

Practical examples:

  • A support team uses the node to automatically create tickets when a private message arrives.
  • A marketing team tracks group chat discussions about a product launch and triggers notifications.
  • A project management workflow reacts only to messages in a specific thread related to a task.

Properties

Name Meaning
Message Filters Select which types of messages to listen for: "Private" (only private messages), "Group" (only group messages). Default is both.
Filter Thread ID Optional string to filter messages by a specific thread ID. Leave empty to receive messages from all threads.

Output

The node outputs JSON data representing the received message(s) that triggered the workflow. The structure includes details such as message content, sender information, message type (private or group), and thread ID if applicable.

If binary data is present in the message (e.g., attachments), it will be included accordingly, but the primary output is JSON describing the message event.

Dependencies

  • Requires connection to a messaging service or platform capable of delivering real-time messages.
  • Needs appropriate API credentials or authentication tokens configured in n8n to access the messaging platform.
  • The node internally uses event listeners to handle incoming messages asynchronously.

Troubleshooting

  • No messages triggering the node:
    Ensure the correct message filters are selected and the thread ID filter (if set) matches existing threads. Also, verify that the messaging service connection and credentials are valid.

  • Authentication errors:
    Check that the API key or authentication token is correctly configured and has sufficient permissions to receive messages.

  • Workflow not starting on message arrival:
    Confirm that the node is properly activated and connected. Review logs for any runtime errors.

  • Unexpected message formats or missing fields:
    Verify that the messaging platform's API version is compatible with the node implementation.

Links and References

Discussion