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
Outbound Messages → Get Message
AI-generatedOverview
This node interacts with the WaliChat 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 particular outbound message by its unique ID. This is useful for scenarios where you want to track message delivery status, review message content, or audit communication history.
Practical examples include:
- Fetching the status and metadata of a sent WhatsApp message to confirm delivery.
- Retrieving associated device, agent, or event details related to the message for troubleshooting or analytics.
- Integrating message data into CRM or support systems to provide context on customer interactions.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the outbound message you want to retrieve. |
| Include | Additional related information to include in the response. Options: Device, Agent, Events |
- Message ID is required and must be provided to specify which message to get.
- Include is optional and allows fetching extra details linked to the message:
- Device: Information about the device that sent the message.
- Agent: Details about the agent (user) who sent or handled the message.
- Events: Related events such as delivery or read receipts.
Output
The output JSON contains detailed information about the requested outbound message. This typically includes:
- Message metadata such as ID, timestamp, status, and content.
- If requested via the "Include" property, nested objects with:
- Device details (e.g., device ID, type).
- Agent information (e.g., user ID, name).
- Event logs related to the message lifecycle.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the WaliChat WhatsApp API.
- Needs an API key credential configured in n8n to authenticate requests.
- No additional environment variables are explicitly required beyond standard API authentication.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Message ID will likely result in an error indicating the message was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
"Message not found": Verify the Message ID is correct and exists in your WaliChat account."Authentication failed": Check that the API key credential is correctly set up and has necessary permissions.- Timeout or network errors: Ensure your server can reach the WaliChat API endpoint and retry.
Links and References
- WaliChat WhatsApp API Documentation (example placeholder, replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes
- General WhatsApp Business API guides for understanding message lifecycle and events.