Actions76
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
- Profile Actions
- LID Actions
- File Actions
Overview
This node integrates with the Wappfy API to interact with WhatsApp groups programmatically. Specifically, the Group - List operation retrieves a paginated list of WhatsApp groups associated with the authenticated session. This is useful for scenarios where you want to manage or analyze group data, such as monitoring group activity, syncing group lists, or automating group-related workflows.
Practical examples:
- Fetching all WhatsApp groups your account is part of to display in a dashboard.
- Automating periodic synchronization of group information into a CRM or database.
- Filtering and processing groups based on creation date or name by using sorting and pagination.
Properties
| Name | Meaning |
|---|---|
| Limit | Number of group items to return in one request (pagination size). Default is 20. |
| Offset | Number of group items to skip before starting to collect the result set (pagination offset). Default is 0. |
| Sort Order | The order in which groups are sorted in the response. Options: Ascending (asc), Descending (desc). Default is Descending. |
Output
The output is an array of JSON objects representing WhatsApp groups. Each object contains details about a group as returned by the Wappfy API's /groups endpoint. Typical fields may include group ID, subject/name, participants count, and other metadata related to each group.
If multiple groups are returned, they are output as separate items in the array.
No binary data is output by this operation.
Dependencies
Requires a valid connection to the Wappfy API, including:
- Base URL of the Wappfy API instance.
- Instance name identifying the WhatsApp session.
- An API key credential for authentication.
The node uses HTTP GET requests to the Wappfy API endpoints.
Proper configuration of credentials in n8n is necessary to authenticate and authorize API calls.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect instance name or base URL will lead to connection errors.
- Exceeding API rate limits may result in temporary blocking or errors.
- Providing invalid values for
limitoroffsetcould cause unexpected results or errors.
Error messages:
- Authentication errors typically indicate problems with the API key or session.
- HTTP 404 errors may mean the instance or resource was not found.
- HTTP 400 errors can occur if parameters like
limitoroffsetare invalid.
Resolutions:
- Verify that the API key credential is correctly set up and active.
- Confirm the instance name matches the active WhatsApp session.
- Check the base URL for correctness and accessibility.
- Use valid numeric values for pagination properties.
- Review API usage limits and adjust request frequency accordingly.
Links and References
- Wappfy API Documentation (for detailed API endpoints and parameters)
- WhatsApp Group Management Concepts (general understanding of WhatsApp groups)
- n8n Documentation (for configuring credentials and using HTTP Request nodes)
This summary covers the static analysis of the node’s execute method focusing on the "Group" resource and "List" operation only, as requested.