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 SMS API to manage SMS messages and campaigns. Specifically, for the SMS resource and Get Sent operation, it retrieves a paginated list of sent SMS messages. This is useful for monitoring outgoing SMS traffic, auditing message delivery, or integrating SMS sending status into workflows.
Practical examples:
- Fetching the last 10 sent SMS messages to verify successful dispatch.
- Paginating through sent SMS logs for reporting or analytics.
- Integrating SMS send history into CRM or support systems.
Properties
| Name | Meaning |
|---|---|
| Limit | Limits the number of sent SMS results returned per page (pagination size). Default is 10. |
| Page | Specifies the page number of results to retrieve (for pagination). Default is 1. |
Output
The node outputs an array of JSON objects representing sent SMS messages. Each item corresponds to one sent SMS record as returned by the Zender API's /get/sms.sent endpoint. The exact structure depends on the API response but typically includes details such as message ID, recipient phone number, message content, timestamp, status, and other metadata related to the sent SMS.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Zender API.
- The node uses HTTP GET requests to the Zender API base URL configured in credentials.
- Pagination parameters (
limitandpage) are passed as query string parameters.
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 cause request timeouts or errors.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; recheck and update credentials.
- "404 Not Found" or similar errors may indicate incorrect API endpoint usage or resource unavailability.
- Rate limiting errors from the API require slowing down request frequency or contacting Zender support.
Links and References
- Zender API Documentation (general reference for endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls