Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node integrates with the Zender API to manage SMS-related operations, specifically for the "Get Campaigns" operation under the SMS resource. It retrieves a paginated list of SMS campaigns from the Zender platform. This is useful for users who want to monitor or analyze their SMS marketing campaigns, track campaign statuses, or integrate campaign data into automated workflows.

Practical examples include:

  • Fetching recent SMS campaigns to display in a dashboard.
  • Automating reports on SMS campaign performance.
  • Triggering follow-up actions based on active or completed campaigns.

Properties

Name Meaning
Limit Limits the number of SMS campaigns returned per page. Default is 10.
Page Specifies the page number for pagination through SMS campaigns. Default is 1 (first page).

Output

The output is a JSON object containing the list of SMS campaigns retrieved from the Zender API. The structure typically includes campaign details such as campaign IDs, names, statuses, and other metadata provided by the API.

Each item in the output corresponds to one input item processed and contains the campaigns data under the json property.

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 endpoint ${baseUrl}/get/sms.campaigns with query parameters for pagination (limit and page).
  • The base URL and API secret are obtained from the configured credentials.
  • No additional environment variables are required beyond the API credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid API keys; verify and update credentials.
    • Rate limiting or quota exceeded errors require checking API usage limits.
    • Unexpected response formats may indicate API changes; ensure the node version is up to date.

  • Resolution tips:

    • Confirm that the API key credential is correctly configured in n8n.
    • Adjust the Limit and Page properties to valid values within the range supported by the API.
    • Check network access and proxy settings if requests fail consistently.

Links and References

Discussion