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
This node interacts with the Wassenger WhatsApp API to manage team members within an organization. Specifically, the "Delete Team Members" operation allows users to remove one or more users from the team. It supports options to handle chats assigned to those users by unassigning, reassigning to another user, or resolving them before deletion. Additionally, it can force delete users even if they have access to WhatsApp numbers and optionally remove them completely from the system.
Common scenarios where this node is beneficial include:
- Cleaning up team members who no longer need access to the WhatsApp system.
- Reassigning chats from departing users to active team members to maintain conversation continuity.
- Enforcing strict user removal policies by forcing deletion despite existing WhatsApp number access.
Practical example:
- A manager wants to remove several users who left the company. They use this node to delete these users, reassign their open chats to a team lead, and ensure that the users are fully removed from the system.
Properties
| Name | Meaning |
|---|---|
| Force Delete | Whether to force delete users even if they have access to one or more WhatsApp numbers (boolean: true/false). |
| Users to Delete | List of users to delete (up to 10). For each user: - Identifier Type: Choose between User ID or Email to identify the user. - User ID: The 24-character hexadecimal ID of the user (if Identifier Type is ID). - Email: Email address of the user (if Identifier Type is Email). - Action: What to do with chats assigned to this user: • Unassign Chats • Reassign Chats • Resolve Chats - Reassign To User ID: If action is "Reassign Chats", specify the User ID to whom chats will be reassigned. - Remove Completely: Whether to remove the user completely from the system even if they have access to other WhatsApp numbers (boolean). |
Output
The node outputs JSON data representing the result of the delete operation for each input item. This typically includes confirmation of deleted users and any relevant status messages returned by the Wassenger API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger API being accessible and properly configured.
- No additional environment variables or external services are explicitly required beyond the API key.
Troubleshooting
Common Issues:
- Attempting to delete users who still have active WhatsApp number access without enabling "Force Delete" may cause the operation to fail.
- Providing invalid user identifiers (wrong format or non-existent IDs/emails) will result in errors.
- Reassigning chats to a non-existent or unauthorized user ID will cause failure in chat reassignment.
Error Messages and Resolutions:
- "User not found": Verify the user identifier (ID or email) is correct.
- "Cannot delete user with active WhatsApp number access": Enable "Force Delete" if you intend to override this restriction.
- "Invalid reassignment user ID": Ensure the reassignment target user exists and has proper permissions.
- Network or authentication errors: Check API key validity and network connectivity.
Links and References
- Wassenger Official API Documentation (for detailed API behavior and error codes)
- n8n Documentation on Creating Custom Nodes