Actions29
- Sessions Actions
- Chats Actions
- Contacts Actions
- Groups Actions
- Messages Actions
Overview
This node connects to a WhatsApp HTTP API to list messages associated with a specific phone session. It is useful for retrieving message history or monitoring incoming and outgoing messages for a given WhatsApp account identified by its session ID (phone number). Practical applications include customer support dashboards, chat analytics, or automated workflows that react to received messages.
Properties
| Name | Meaning |
|---|---|
| Phone | The session ID representing the WhatsApp phone number to list messages for. This is required and typically set from credentials. |
Output
The node outputs JSON data containing the list of messages retrieved from the WhatsApp API for the specified session. The exact structure depends on the API response but generally includes message details such as sender, receiver, timestamp, and content. There is no indication that binary data is output.
Dependencies
- Requires connection to a WhatsApp HTTP API service.
- Needs an API URL and authentication credentials configured in n8n (e.g., an API key or token).
- The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Missing or invalid session ID: Ensure the "Phone" property is correctly set and corresponds to a valid WhatsApp session.
- Authentication errors: Verify that the API credentials are correct and have sufficient permissions.
- API connectivity issues: Check network access to the WhatsApp API endpoint and confirm the base URL is properly configured.
- Unexpected API responses: Confirm the API version matches what the node expects and that the session has message history available.
Links and References
- Refer to your WhatsApp HTTP API provider’s documentation for detailed information on message listing endpoints and response formats.
- n8n documentation on creating and configuring HTTP API nodes may provide additional guidance.