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. This is useful in scenarios such as:
- Automating responses to private messages from customers.
- Monitoring group chats for certain keywords or events.
- Filtering notifications to only process messages from a particular thread.
For example, a user could configure the node to trigger a workflow whenever a new private message arrives in a specific thread, enabling personalized automated replies or logging.
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. If empty, messages from all threads are received. |
Output
The node outputs JSON data representing the incoming message event. The structure includes details about the message, such as its content, sender, type (private or group), and thread ID. This allows subsequent nodes in the workflow to access message information for processing.
No binary data output is indicated.
Dependencies
- Requires connection to an external messaging service that provides real-time message events.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the messaging platform.
- The node depends on the messaging service's API to receive message events and filter them accordingly.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials can prevent the node from receiving messages.
- Specifying an invalid or non-existent thread ID in the filter will result in no messages triggering the workflow.
- Network connectivity issues may cause delays or failures in receiving message events.
Error Messages:
- Authentication errors indicate problems with API keys or tokens; verify and update credentials.
- Timeout or connection errors suggest network problems; check internet access and firewall settings.
- No messages received despite configuration may mean filters are too restrictive; try broadening filter criteria.
Links and References
- Refer to your messaging service's API documentation for details on message event structures and authentication.
- n8n documentation on webhook and trigger nodes for general guidance on event-driven workflows.