Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
The node operation "Accept Group Member Requests" allows users to approve membership requests for a specific group chat. This is useful in scenarios where group administrators want to programmatically manage who can join their groups, automating the acceptance of pending member requests without manual intervention.
Practical examples include:
- Automatically approving trusted users or bots into a group.
- Managing large community groups by bulk accepting multiple join requests.
- Integrating with external systems that trigger group membership approvals based on certain criteria.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID, a numeric identifier for the particular instance of the node execution. |
| Chat Id | The unique identifier of the group chat in the format <groupId>@g.us. |
| Requester Ids | One or more requester IDs representing users whose membership requests are to be approved. |
Output
The node outputs JSON data representing the result of the accept request operation. This typically includes confirmation of which requester IDs were accepted and any relevant status messages from the API.
If the node supports binary data output, it would relate to attachments or media associated with the group or requests, but this is not indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authenticating with the WaAPI service.
- Depends on the external WaAPI REST API endpoint at
https://waapi.app/api/v1. - Uses HTTP headers specifying JSON content type and acceptance.
- The node relies on the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration.
Troubleshooting
- Common issues:
- Invalid or missing
Chat Idformat may cause the API to reject the request. - Providing incorrect or unauthorized requester IDs will result in failure to approve those members.
- Network or authentication errors if the API key is invalid or missing.
- Invalid or missing
- Error messages:
- Authentication errors indicating invalid API credentials require checking and updating the API key.
- Validation errors about the
Chat IdorRequester Idsshould prompt verifying the input formats. - Rate limiting or quota exceeded errors from the API suggest reviewing usage limits.
Links and References
- WaAPI Official Documentation (for detailed API usage)
- n8n OpenAPI Node Integration Guide