Actions7
- Text Message Actions
- Media Message Actions
- Group Message Actions
- Message Management Actions
Overview
This node integrates with the OneSender API to manage WhatsApp messages. Specifically, for the Message Management resource and Get Messages operation, it retrieves a list of WhatsApp messages from the OneSender service. It supports filtering, pagination, sorting, and limiting the number of returned messages.
Common scenarios where this node is useful include:
- Fetching recent WhatsApp messages for monitoring or logging.
- Searching messages by text content.
- Paginating through large sets of messages.
- Sorting messages by date or ID in ascending or descending order.
For example, a user might want to retrieve the last 100 messages containing a specific keyword, sorted by date descending, to analyze customer interactions.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available messages or limit the results to a specified number. |
| Limit | Maximum number of messages to return when "Return All" is false. |
| Filters | Collection of filters to refine the message retrieval: |
| - Page | Page number of results to fetch (for pagination). |
| - Per Page | Number of messages per page. |
| - Search | Text string to search within messages. |
| - Sort By | Field to sort messages by; options are "Date" or "ID". |
| - Sort Order | Order of sorting; options are "Ascending" or "Descending". |
Output
The output is an array of JSON objects representing WhatsApp messages retrieved from the OneSender API. Each object corresponds to a message and contains its details as provided by the API.
The exact structure depends on the OneSender API response but typically includes fields such as message ID, sender, recipient, timestamp, message content, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the OneSender API via an API key credential.
- The node uses the base URL and API key from the configured credentials to authenticate requests.
- No additional environment variables or external services are required beyond the OneSender API access.
Troubleshooting
Common Issues:
- Invalid or missing API key will cause authentication failures.
- Requesting too many messages without proper pagination may lead to timeouts or rate limits.
- Incorrect filter parameters (e.g., invalid page number) may result in empty or error responses.
Error Messages:
- Authentication errors typically indicate issues with the API key; verify the credential configuration.
- HTTP errors from the API (4xx or 5xx) should be checked against OneSender API documentation for causes.
- If the node throws an error about invalid parameters, review the input properties for correctness.
Resolution Tips:
- Ensure the API key credential is correctly set up and has necessary permissions.
- Use pagination filters to limit the size of each request.
- Validate filter values before running the node.
Links and References
- OneSender API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)