Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node allows you to retrieve a specific message by its unique serialized ID from the WaAPI service. It is useful when you need to fetch detailed information about a particular message, including optionally its media content, for purposes such as auditing, processing, or displaying message details in workflows.
Practical examples:
- Fetching a chat message to analyze its content or metadata.
- Retrieving media attached to a message for further processing or storage.
- Integrating message data into other systems or reports.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier for the instance). |
| Message Id | Serialized message ID in the format <fromMe>_<chatId>_<messageHash>. This uniquely identifies the message to retrieve. |
| Include Media | Boolean option to include base64 encoded media content in the response when set to true. |
Output
The node outputs JSON data representing the requested message. The structure includes all message details as returned by the WaAPI service, such as sender info, timestamps, text content, and other metadata.
If "Include Media" is enabled, the output will also contain the media content encoded in base64 format within the JSON response.
No binary data output is produced; media content is embedded as base64 strings inside the JSON.
Dependencies
- Requires an API key credential for authenticating with the WaAPI service.
- The node communicates with the WaAPI REST API endpoint at
https://waapi.app/api/v1. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Invalid or missing Message Id: Ensure the message ID follows the required serialized format
<fromMe>_<chatId>_<messageHash>. Incorrect formatting will cause errors. - Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Message not found: If the message ID does not exist or is inaccessible, the node may return an error or empty result.
- Large media content: Including media can increase response size significantly; consider this if workflow performance is impacted.
- Network issues: Check connectivity to the WaAPI endpoint if requests time out or fail.
Links and References
- WaAPI Official Documentation (for detailed API usage and message ID formats)
- n8n Documentation (for general node usage and credential setup)