Zender icon

Zender

Interact with Zender WhatsApp API

Overview

This node integrates with the Zender WhatsApp API to manage WhatsApp groups and perform various operations related to them. Specifically, for the Group resource with the Get All operation, it retrieves all WhatsApp groups associated with a specified WhatsApp account.

This functionality is useful when you want to list or manage WhatsApp groups linked to your Zender WhatsApp account within an automation workflow. For example, you might want to fetch all groups to display them in a dashboard, synchronize group data with another system, or use group information as part of a messaging campaign.

Properties

Name Meaning
Account ID Zender WhatsApp Account ID (unique identifier for your WhatsApp account). Required to specify which WhatsApp account's groups to retrieve.

Output

The output is a JSON object containing the response from the Zender API endpoint that lists WhatsApp groups. The structure depends on the API but typically includes details about each group such as group IDs, names, and possibly metadata related to the groups.

Example output structure (simplified):

{
  "groups": [
    {
      "id": "group1",
      "name": "Friends",
      "membersCount": 10,
      ...
    },
    {
      "id": "group2",
      "name": "Work",
      "membersCount": 25,
      ...
    }
  ]
}

No binary data output is involved in 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 environment variables are required beyond the API credential setup.

Troubleshooting

  • Missing or invalid Account ID: Since the Account ID is required, ensure it is correctly provided. An incorrect or missing Account ID will cause the API call to fail.
  • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
  • API connectivity issues: Network problems or incorrect base URL configuration can cause request failures.
  • API rate limits: If many requests are made in a short time, the API may throttle requests; handle such errors by retrying after some delay.
  • Unexpected API responses: Check the API documentation for any changes or updates if the output format differs.

If the node throws an error, enabling "Continue On Fail" in n8n can help process multiple items without stopping the entire workflow.

Links and References


Note: This summary focuses exclusively on the Group resource with the Get All operation as requested.

Discussion