Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

This node interacts with the Zender API to manage SMS messages and campaigns. Specifically, for the SMS resource and Get Pending operation, it retrieves a paginated list of pending SMS messages that are queued or awaiting processing.

Common scenarios where this node is beneficial include:

  • Monitoring SMS messages that have not yet been sent or processed.
  • Building workflows that react to pending SMS messages, such as alerting or retry mechanisms.
  • Integrating SMS status checks into broader communication automation pipelines.

Example use case:

  • A marketing team wants to check which SMS messages are still pending before launching a new campaign, ensuring no messages are stuck in the queue.

Properties

Name Meaning
Limit Limits the number of pending SMS results returned per page (pagination size).
Page Specifies the page number of results to retrieve (for pagination).

These properties control how many pending SMS messages are fetched and from which page in the result set.

Output

The output is a JSON object containing the data returned by the Zender API endpoint for pending SMS messages. This typically includes an array or list of SMS message objects with details such as message ID, recipient phone number, message content, status, timestamps, and other metadata related to each pending SMS.

No binary data output is involved in 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 appended with /get/sms.pending.
  • Pagination parameters (limit and page) are passed as query string parameters.
  • Proper configuration of the Zender API credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Requesting a page number beyond available pages 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 on the Zender account.
    • Unexpected response formats or empty responses might indicate changes in the API or incorrect parameters.

  • Resolution tips:

    • Ensure the API key credential is correctly configured and active.
    • Adjust Limit and Page values to valid ranges.
    • Check network access and firewall settings if requests fail.
    • Review Zender API documentation for any updates or changes.

Links and References

Discussion