WhatsApp - Trigger
AI-generatedOverview
This node acts as a trigger for WhatsApp events using the WhatsApp BR API. It listens for various WhatsApp-related events such as received or sent messages, media, reactions, group changes, contact updates, calls, and presence updates. Users can filter events by a specific WhatsApp session or select which types of events to receive. When an event matching the filter criteria occurs, the node outputs the event data to the workflow. This is useful for automating workflows based on WhatsApp interactions, such as responding to messages, tracking group activity, or monitoring call events.
Use Case Examples
- Automate customer support by triggering workflows when a message is received in a specific WhatsApp session.
- Track group membership changes by triggering workflows on group join or leave events.
- Monitor message status updates to log delivery and read receipts.
Properties
| Name | Meaning |
|---|---|
| Sessão | Filter events by a specific WhatsApp session; leave empty to receive events from all sessions. |
| Eventos Avançados | Select additional WhatsApp event types to trigger on, beyond just messages. Includes options like message received, message sent, media received, group updates, calls, and presence changes. |
Output
JSON
event- The type of WhatsApp event received, e.g., message_received, group_join.sessionName- The name of the WhatsApp session from which the event originated.from- The sender or source of the event.body- The content of the message or event body, if applicable.message- The message content if present in the event data.
Dependencies
- Requires credentials for WhatsApp BR API including API URL and Bearer Token for authentication.
Troubleshooting
- Authentication errors (401) indicate invalid or missing Bearer Token; verify credentials configuration.
- API not found errors (404) suggest incorrect API URL; check the API endpoint URL in credentials.
- Connection refused errors indicate the API server is unreachable; ensure the API service is running and accessible.
- Event filtering may cause no data output if the session or event type does not match the configured filters.