Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
The node integrates with the Zender API to manage SMS messages and campaigns. Specifically, for the SMS - Get Received operation, it retrieves a paginated list of received SMS messages from the Zender platform.
This operation is useful in scenarios where you want to monitor incoming SMS messages, such as customer replies, notifications, or alerts. For example, a business could use this node to fetch all received SMS messages daily to process customer feedback or automate responses.
Properties
| Name | Meaning |
|---|---|
| Limit | Limits the number of received SMS messages returned per page. Default is 10. |
| Page | Specifies the page number for pagination through the received SMS messages. Default is 1. |
Output
The output is a JSON object containing the data returned by the Zender API endpoint /get/sms.received. This typically includes an array of received SMS message records with details such as sender phone number, message content, timestamp, and status.
The exact structure depends on the Zender API response but generally includes:
- Message ID
- Sender phone number
- Message text
- Timestamp of receipt
- Status or delivery information
No binary data is output 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 pages 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; verify and update credentials.
- Rate limiting errors may occur if too many requests are made; implement retries or backoff.
- If the node throws an error about missing parameters, ensure that
LimitandPageare set correctly.
Links and References
- Zender API Documentation (general reference for endpoints)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls