Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
This node interacts with the Zender WhatsApp API to manage contacts and their groups, among other communication-related resources. Specifically, for the Contact resource with the Get Groups operation, it retrieves a paginated list of all contact groups associated with the user's WhatsApp account.
Typical use cases include:
- Fetching all contact groups to display or process them in workflows.
- Managing group memberships by first retrieving existing groups.
- Integrating with other systems that require up-to-date contact group information from WhatsApp.
For example, you might use this node to get all contact groups before sending targeted messages to specific groups or to synchronize group data with a CRM system.
Properties
| Name | Meaning |
|---|---|
| Limit | Limits the number of contact groups returned per page. Default is 10. |
| Page | Specifies the page number for pagination to retrieve different sets of contact groups. Default is 1. |
Output
The output is a JSON object containing the response from the Zender API endpoint /get/groups. This typically includes an array of contact groups with their details such as group IDs, names, and possibly metadata related to each group.
The exact structure depends on the API response but generally looks like:
{
"groups": [
{
"id": "string",
"name": "string",
// other group properties
},
...
],
"pagination": {
"page": 1,
"limit": 10,
"total": 100
}
}
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Zender WhatsApp API.
- The node needs an API key credential (referred generically as "an API key credential") configured in n8n to authenticate requests.
- The base URL for the API is taken from the credentials configuration.
- Pagination parameters (
limitandpage) control the amount of data fetched per request.
Troubleshooting
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Ensure the API key is correctly set up in n8n credentials.
- Pagination issues: Requesting a page number beyond the available range may return empty results. Adjust the
pageparameter accordingly. - API rate limits: Excessive requests may be throttled by the Zender API. Implement delays or reduce request frequency if encountering rate limit errors.
- Network errors: Connectivity issues can cause request failures. Verify network access to the Zender API endpoint.
- Unexpected API responses: If the API changes or returns unexpected data, the node may not parse it correctly. Check the API documentation or update the node accordingly.
Links and References
- Zender WhatsApp API Documentation (generic link, replace with actual if available)
- n8n Documentation: Creating Custom Nodes
- Pagination concepts: API Pagination Best Practices
This summary focuses on the Contact resource's Get Groups operation as requested, based on static analysis of the provided source code and input property definitions.