WhatsApp - Multi Trigger
AI-generatedOverview
This node acts as a multi-trigger for WhatsApp messages, receiving incoming messages and routing them to one of six outputs based on the message type: Text, Image, Audio, Video, Document, or Others. It supports filtering messages by session and optionally accepting messages from group chats. This node is useful for workflows that need to handle different types of WhatsApp messages separately, such as processing images differently from text or audio messages.
Use Case Examples
- A customer support workflow that routes text messages to a chatbot, images to a human agent, and documents to a file storage system.
- A marketing automation workflow that triggers different actions based on whether the incoming message is a video or an audio message.
Properties
| Name | Meaning |
|---|---|
| acceptGroups | Determines whether to accept messages from group chats. If false, group messages are ignored; if true, group messages are processed. |
| sessionFilter | Filters incoming messages by a specific WhatsApp session. If empty, messages from all sessions are accepted. |
Output
JSON
json- The full incoming message event data received from WhatsApp.
Dependencies
- Requires credentials for WhatsApp BR API including an API URL and a Bearer Token for authentication.
Troubleshooting
- If webhook registration fails with a 401 error, check that the Bearer Token in the credentials is correct and not expired.
- If webhook registration fails with a 404 error, verify that the API URL in the credentials is correct and does not include extra path segments like /api or /webhooks.
- If connection is refused, ensure the WhatsApp BR API service is running and accessible at the configured URL.
- Group messages may be filtered out if 'acceptGroups' is set to false, which is the default behavior.