Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
This node interacts with the Zender WhatsApp API to manage chat messages and related data. Specifically, for the Chat resource with the Get Sent operation, it retrieves a paginated list of sent WhatsApp chat messages. This is useful for scenarios where you want to review or process messages that have been sent from your WhatsApp account via Zender.
Practical examples include:
- Auditing sent messages for compliance or record-keeping.
- Triggering follow-up workflows based on sent message history.
- Analyzing messaging patterns or delivery success rates.
Properties
| Name | Meaning |
|---|---|
| Limit | The maximum number of sent chat results to retrieve per page (pagination size). |
| Page | The page number of results to retrieve, used for pagination through sent chat messages. |
Output
The output is an array of JSON objects representing sent WhatsApp chat messages retrieved from the Zender API. Each item corresponds to one sent chat message entry as returned by the API endpoint /get/wa.sent.
The exact structure depends on the API response but typically includes details such as message ID, recipient, timestamp, message content, status, and other metadata related to the sent chats.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Zender WhatsApp API.
- Requires an API key credential (referred generically as "an API key credential") configured in n8n for authentication.
- The base URL for the Zender API must be set in the credentials.
- Uses HTTP GET requests with query parameters
limitandpagefor pagination.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Requesting a page number beyond available data may return empty results.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Rate limiting or quota exceeded errors require checking API usage limits with Zender.
- If the node throws an error about missing parameters, ensure both
LimitandPageare set correctly.
Resolution tips:
- Confirm API credentials are correct and have necessary permissions.
- Adjust pagination parameters to valid ranges.
- Enable "Continue On Fail" in the node settings to handle intermittent errors gracefully.
Links and References
- Zender WhatsApp API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- Pagination best practices in APIs: Pagination