Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node operation allows you to deny membership requests to a specific group in a messaging platform. It is useful when managing group memberships and controlling who can join your group by explicitly rejecting certain users' requests. For example, if you run a private community or team chat, you can use this operation to automatically or manually deny access to unwanted or unauthorized users.
Properties
| Name | Meaning |
|---|---|
| Id | The instance ID of the node execution context (usually an internal identifier). |
| Chat Id | The unique identifier of the group chat where member requests are being denied. |
| Requester Ids | One or more user IDs representing the members whose join requests should be denied. |
- Chat Id typically looks like
<xxxxx>@g.us, identifying the group. - Requester Ids are user identifiers in the format similar to
1234567890@c.us.
Output
The node outputs JSON data reflecting the result of the deny request operation. This usually includes confirmation that the specified requester(s) have been denied membership to the group. The exact structure depends on the API response but generally contains status information about the denial action.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the WaAPI service.
- The node communicates with the WaAPI endpoint at
https://waapi.app/api/v1. - Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Chat Id or Requester Ids will cause the operation to fail.
- Insufficient permissions or invalid API credentials may result in authentication errors.
- Network connectivity problems can prevent communication with the WaAPI service.
Error messages:
- Authentication failures typically indicate incorrect or missing API keys; verify and update credentials.
- "Invalid chat ID" or "Invalid requester ID" errors suggest malformed or non-existent identifiers; double-check input values.
- Timeout or connection errors imply network issues; ensure stable internet access and correct endpoint URL.
Links and References
- WaAPI Official Documentation (for detailed API usage and parameters)
- n8n Documentation (for general node and credential setup guidance)