Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node operation "Get Message Info By Id" retrieves detailed information about a specific message using its unique serialized message ID. It is useful when you need to fetch metadata or status of a particular message in a chat system, for example, to verify delivery status, read receipts, or message content details.
Practical examples include:
- Fetching the status of a sent message to confirm if it was delivered or read.
- Retrieving message metadata for logging or auditing purposes.
- Accessing message details to display in a custom dashboard or interface.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier) used internally to specify the instance context. |
| Message Id | Serialized message identifier in the format <fromMe>_<chatId>_<hash>. This uniquely identifies the message to retrieve. |
Output
The output JSON contains detailed information about the requested message. This typically includes fields such as message content, sender info, timestamps, delivery and read status, and other metadata related to the message.
If the node supports binary data output (not explicitly shown here), it would represent any media or attachments associated with the message.
Dependencies
- Requires an API key credential for authenticating requests to the WaAPI service.
- The node communicates with the external WaAPI REST API endpoint at
https://waapi.app/api/v1. - Proper configuration of this API key credential within n8n is necessary for successful execution.
Troubleshooting
- Invalid or missing Message Id: Ensure the
Message Idproperty is correctly formatted as<fromMe>_<chatId>_<hash>. An incorrect format will cause the API to reject the request. - Authentication errors: Verify that the API key credential is set up correctly and has not expired.
- Network issues: Confirm that your environment can reach the
https://waapi.app/api/v1endpoint without firewall or proxy blocking. - Instance ID mismatch: If multiple instances are used, ensure the correct
Idis provided to avoid fetching wrong data.
Links and References
- WaAPI Official Documentation (for API details and message ID formats)
- n8n Credential Setup Guide (for configuring API keys)