Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node interacts with the Zender WhatsApp API to manage contacts and other related resources. Specifically, for the Contact resource with the Get Contacts operation, it retrieves a paginated list of contacts from the Zender service.

This operation is useful when you want to fetch your stored WhatsApp contacts managed via Zender, for example, to display them, process them further in workflows, or synchronize contact data with other systems.

Practical examples:

  • Fetching a limited number of contacts per page to display in a dashboard.
  • Automating contact synchronization between Zender and a CRM system.
  • Retrieving contacts to send targeted WhatsApp campaigns.

Properties

Name Meaning
Limit The maximum number of contacts to retrieve per page. Default is 10.
Page The page number for pagination to specify which subset of contacts to retrieve. Default is 1.

Output

The output is a JSON object containing the response from the Zender API endpoint /get/contacts. This typically includes an array of contact objects along with any metadata related to pagination (such as total count, current page, etc.).

Each contact object generally contains details like phone number, name, assigned groups, and other relevant contact information managed by Zender.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses HTTP requests to communicate with the Zender API endpoints.
  • The base URL and API secret are obtained from the configured credentials.
  • No additional external dependencies beyond the Zender API and n8n's HTTP request helpers.

Troubleshooting

  • Common issues:

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

  • Error messages:

    • Authentication errors usually indicate invalid API keys or expired tokens; verify and update credentials.
    • Rate limiting or quota exceeded errors require checking your Zender account limits.
    • "Not Found" or similar errors might occur if the resource does not exist or parameters are incorrect.

  • Resolution tips:

    • Ensure the API key credential is correctly set up in n8n.
    • Use valid pagination values within the range of available data.
    • Check network access and firewall settings to allow outbound API calls.

Links and References

Discussion