Actions37
- Instance Actions
- Message Actions
- Group Actions
- Contact Actions
- Chat Actions
- Campaign Actions
- Chatbot Actions
Overview
This node integrates with the UazAPI service to manage WhatsApp groups programmatically. Specifically, the "Group" resource with the "Get Info" operation allows users to retrieve detailed information about a specific WhatsApp group by providing its unique Group JID (Jabber ID). This is useful for scenarios where you need to fetch metadata or status about a group, such as its name, participants, description, or other attributes managed by the WhatsApp instance.
Practical examples include:
- Automating the retrieval of group details before sending targeted messages.
- Monitoring group membership or settings changes.
- Integrating group info into dashboards or CRM systems.
Properties
| Name | Meaning |
|---|---|
| Group JID | The unique identifier of the WhatsApp group in JID format (e.g., 120363308883996631@g.us). This is required to specify which group's information to retrieve. |
Output
The output is a JSON object containing the response from the UazAPI endpoint /group/info. This typically includes detailed information about the specified WhatsApp group, such as:
- Group metadata (name, description, creation date).
- List of participants and their roles.
- Group settings and status.
The exact structure depends on the UazAPI response but generally provides comprehensive group details.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the UazAPI service.
- Requires valid API credentials configured in n8n for authentication with UazAPI.
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP requests authenticated via these credentials to communicate with UazAPI endpoints.
Troubleshooting
- Invalid or missing Group JID: Ensure the Group JID is correctly provided in the input property. It must be the full JID string including the domain suffix (e.g.,
@g.us). - Authentication errors: Verify that the API credentials are correctly set up and have the necessary permissions.
- Network or connectivity issues: Confirm that the n8n instance can reach the UazAPI base URL.
- Unexpected API responses: Check if the group exists and the bot/user associated with the API has access to it.
- If the node throws errors related to HTTP requests, inspect the error message for clues such as 4xx or 5xx HTTP status codes and adjust inputs or credentials accordingly.
Links and References
- UazAPI Documentation (for detailed API endpoint descriptions)
- WhatsApp Group JID format explanation: Generally, group JIDs end with
@g.usindicating a WhatsApp group.
This summary is based solely on static analysis of the provided source code and property definitions.