Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
The "Reject Members" operation under the "Groups" resource allows users to reject pending membership requests in WhatsApp groups managed via the Wassenger WhatsApp API. This node is useful for administrators who want to control group membership by selectively rejecting certain phone numbers or rejecting all pending members at once.
Practical scenarios include:
- Automatically rejecting spam or unauthorized join requests to a WhatsApp group.
- Managing group membership approvals programmatically based on custom business logic.
- Bulk rejecting all pending members when cleaning up group membership requests.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the group is managed. |
| Group ID | The unique identifier of the WhatsApp group where members are to be rejected. |
| Approve All | Boolean flag indicating whether to reject all pending members in the group (true means reject all). |
| Phone Numbers | List of phone numbers to reject individually (used only if "Approve All" is false). Format example: +1234567890 |
Output
The node outputs JSON data representing the result of the reject members operation. This typically includes confirmation of which members were rejected or an error message if the operation failed. The output structure depends on the underlying API response but generally confirms success or failure of the rejection request.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Wassenger WhatsApp API using a valid API key credential.
- The node depends on dynamic loading of WhatsApp devices and groups, so proper configuration and permissions to access these resources are necessary.
- The environment must have network access to the Wassenger API endpoints.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number (device) ID can cause failures in identifying the correct source device.
- Incorrect or expired group ID will prevent the operation from targeting the intended group.
- Providing phone numbers in an incorrect format may lead to rejection failures.
- Attempting to reject members when there are no pending members might return empty results or errors.
Error messages:
- Errors related to authentication usually indicate invalid or missing API credentials.
- "Group not found" or similar errors suggest the group ID does not exist or is inaccessible.
- Validation errors on phone numbers indicate formatting issues; ensure numbers include country codes and are properly formatted.
Resolutions:
- Verify API key credentials and refresh if needed.
- Confirm the WhatsApp number and group IDs are correct and accessible.
- Use the node's options to load devices and groups dynamically to avoid manual input errors.
- Ensure phone numbers are in international format with "+" prefix.