Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node interacts with the Wassenger WhatsApp API to retrieve detailed delivery information about a specific WhatsApp message sent from a particular WhatsApp number. It is useful in scenarios where users need to track the status and delivery details of messages they have sent via WhatsApp, such as confirming if a message was delivered, read, or failed.
Practical examples include:
- Customer support teams verifying whether their WhatsApp messages reached customers.
- Marketing automation workflows checking message delivery before triggering follow-up actions.
- Analytics dashboards aggregating message delivery statistics for reporting.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the message was sent. |
| Message ID | The unique hexadecimal ID of the WhatsApp message whose delivery info is being retrieved. |
Output
The node outputs a JSON object containing the delivery information of the specified WhatsApp message. This typically includes fields such as delivery status, timestamps, and possibly acknowledgments related to the message lifecycle on WhatsApp.
If the node supports binary data output (not explicitly shown in the provided code), it would represent any media or file attachments related to the message delivery info, but this is not indicated here.
Dependencies
- Requires an active Wassenger WhatsApp API key credential configured in n8n.
- Depends on the Wassenger API service being accessible and properly authenticated.
- The node uses internal methods from the bundled
chatMessagesaction module to perform the operation.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp Number or Message ID parameters will cause errors.
- Network or authentication failures with the Wassenger API can prevent retrieval of message info.
- If the message ID does not exist or is incorrect, the API may return an error or empty result.
Error messages:
- Errors related to invalid credentials usually indicate misconfigured API keys.
- "Message not found" or similar errors suggest the provided Message ID is incorrect or the message no longer exists.
- Timeout or connection errors imply network issues or API downtime.
Resolutions:
- Verify that the WhatsApp Number and Message ID are correct and correspond to existing entities.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and Wassenger API status.
Links and References
- Wassenger Official API Documentation (for detailed API endpoints and message delivery info)
- n8n Documentation (for general usage of custom nodes and credentials)