Actions10
- Message Actions
- Chat Actions
- User Actions
Overview
This node integrates with the WhatsApp Outreach service by Boost.space, enabling users to interact programmatically with WhatsApp messages, chats, and user profiles. Specifically, the Message - Get One operation retrieves detailed information about a single WhatsApp message by its unique ID.
Common scenarios for this operation include:
- Fetching the content and metadata of a specific WhatsApp message for auditing or processing.
- Retrieving message details to trigger follow-up workflows based on message content.
- Accessing message data for reporting or analytics purposes.
For example, you might use this node to get the full details of a customer inquiry message received via WhatsApp, then route that information into a CRM or support ticket system.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the WhatsApp message to retrieve. This is required to specify which message's details should be fetched. |
Output
The node outputs a JSON object representing the retrieved WhatsApp message. This typically includes all relevant message fields such as sender info, timestamp, message content, attachments metadata (if any), and status.
If the message contains binary attachments, those are not returned in this operation; it only fetches message metadata and text content.
The output JSON structure corresponds directly to the response from the WhatsApp Outreach API's getMessage endpoint.
Dependencies
- Requires an active connection to the WhatsApp Outreach API provided by Boost.space.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node sends POST requests to a fixed base URL (
https://rnmqfhwsqojadktbxnrf.supabase.co/functions/v1) with appropriate endpoints.
Troubleshooting
- Invalid or missing Message ID: If the
Message IDproperty is empty or incorrect, the API will likely return an error indicating the message was not found. Ensure the ID is correct and corresponds to an existing message. - Authentication errors: If the API key credential is invalid or expired, requests will fail with authorization errors. Verify the API key configuration in n8n.
- Network issues: Connectivity problems to the API endpoint can cause timeouts or request failures. Check network access and proxy settings if applicable.
- API rate limits: Excessive requests may be throttled by the API. Implement retry logic or reduce request frequency if encountering rate limit errors.
Links and References
- Boost.space WhatsApp Outreach API Documentation (hypothetical link, replace with actual if available)
- n8n HTTP Request Node Documentation – for understanding how API calls are made within n8n nodes.