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 details about outbound messages sent via the platform. Specifically, the "Get Message" operation under the "Outbound Messages" resource fetches information about a single outbound message by its unique ID. This is useful for scenarios where you want to verify the status, content, or metadata of a previously sent WhatsApp message.
Practical examples include:
- Checking delivery status or read receipts of a specific message.
- Retrieving message details for logging or auditing purposes.
- Including related entities such as the device that sent the message, the agent responsible, or events associated with the message.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the outbound message to retrieve. |
| Include | Additional related information to include in the response. Options: Device, Agent, Events |
Output
The output JSON contains detailed information about the requested outbound message. This includes core message data such as content, timestamps, status, and identifiers.
If selected via the "Include" property, the output may also contain nested objects with additional context:
- Device: Information about the device that sent the message.
- Agent: Details about the agent (user) who handled or sent the message.
- Events: A list or log of events related to the message lifecycle (e.g., delivery, read).
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the external Wassenger service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API key.
Troubleshooting
Common issues:
- Invalid or missing Message ID will cause the API call to fail.
- Network connectivity problems can prevent successful API communication.
- Insufficient permissions or invalid API key will result in authentication errors.
Error messages:
- Errors returned from the API typically include descriptive messages; ensure the Message ID exists and is correct.
- Authentication failures suggest checking the API key credential configuration.
- If the node throws an error about missing parameters, verify that the Message ID is provided and non-empty.
Links and References
- Wassenger Official API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general guidance on using custom nodes and credentials)