Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The "Get Unsubscribed" operation of the Contact resource in this node retrieves a paginated list of contacts who have unsubscribed from communications. This is useful for managing contact lists by identifying users who no longer wish to receive messages, ensuring compliance with communication preferences and regulations.

Typical use cases include:

  • Cleaning up contact lists by filtering out unsubscribed contacts.
  • Reporting or auditing unsubscribed users.
  • Integrating with other systems to update subscription status.

For example, you might use this operation to fetch the first 10 unsubscribed contacts on page 1 to review or export them.

Properties

Name Meaning
Limit The maximum number of unsubscribed contacts to retrieve per page. Default is 10.
Page The page number for pagination to navigate through multiple pages of results. Default is 1.

Output

The output is a JSON object containing the list of unsubscribed contacts retrieved from the API. The exact structure depends on the external service's response but typically includes details such as contact identifiers, phone numbers, names, and unsubscribe status.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Zender WhatsApp API.
  • The node uses HTTP GET requests to the endpoint /get/unsubscribed with query parameters for pagination (limit and page).
  • Proper configuration of the API base URL and credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials 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.
    • Unexpected response formats may indicate changes in the external API; verify API documentation and update the node if needed.

Links and References

Discussion