Actions148
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Files Actions
- Team Actions
- Labels Actions
- Departments 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
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
Overview
This node interacts with the SparkBot WhatsApp API to retrieve detailed delivery information about specific WhatsApp chat messages. It is particularly useful for scenarios where you need to track message status, confirm delivery, or audit message flow within WhatsApp conversations managed via SparkBot.
For example, a customer support team could use this node to verify if a critical notification message was successfully delivered to a clientβs WhatsApp number, enabling better follow-up actions.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the message was sent or received. |
| Message ID | The unique hexadecimal ID of the WhatsApp message whose delivery info is being retrieved. |
Output
The node outputs JSON data containing the delivery information of the specified WhatsApp message. This typically includes details such as delivery status, timestamps, and possibly read receipts or acknowledgments related to that message.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate with the SparkBot WhatsApp API.
- The node depends on the SparkBot service being accessible and properly configured.
- The "WhatsApp Number" must be a valid device ID registered in the SparkBot system.
- The "Message ID" must correspond to an existing message in the WhatsApp conversation history.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp Number or Message ID parameters will cause errors.
- Network connectivity issues or incorrect API credentials can lead to authentication failures.
- Requesting delivery info for a non-existent or deleted message may return empty or error responses.
Error Messages:
- Errors indicating invalid credentials suggest checking the API key configuration.
- "Message not found" or similar errors indicate the provided Message ID does not exist or is inaccessible.
- Timeout or network errors require verifying internet connection and SparkBot API availability.
Links and References
- SparkBot WhatsApp API Documentation (general reference for API capabilities)
- n8n Documentation on Creating Custom Nodes