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-related operations, specifically focusing on revoking a user's access to a device (WhatsApp number) within a team. It is useful in scenarios where an administrator needs to remove or restrict a team member's access to a particular WhatsApp device, for example, when an employee leaves the company or changes roles.
Practical examples include:
- Revoking access of a user identified by their user ID or email from a specific WhatsApp number.
- Choosing how to handle chats assigned to the revoked user, such as unassigning them, reassigning to another user, or resolving them.
- Optionally removing the user completely from the system after revoking access.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which to revoke the user's access. |
| User Identifier Type | The type of identifier used to specify the user: either "User ID" (a 24-character hexadecimal string) or "Email". |
| User ID | The unique ID of the user to revoke access from (required if "User Identifier Type" is "User ID"). |
| The email address of the user to revoke access from (required if "User Identifier Type" is "Email"). | |
| Action | The action to perform on the chats assigned to this user upon revocation. Options are: "Unassign Chats", "Reassign Chats", or "Resolve Chats". |
| Reassign To User ID | If the action is "Reassign Chats", this specifies the user ID to whom the chats should be reassigned. |
| Remove Completely | A boolean flag indicating whether to remove the user completely from the system after revoking access. |
Output
The node outputs JSON data representing the result of the revoke device access operation. This typically includes confirmation of the action taken, any relevant status messages, and details about the affected user and device.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger API endpoints related to team management.
- Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent user ID or email will cause the operation to fail.
- Specifying a WhatsApp number (device) that the authenticated API key does not have access to will result in authorization errors.
- If the "Reassign Chats" action is selected but no valid reassignment user ID is provided, the operation will error out.
Error Messages:
- Errors related to missing required parameters (e.g., user ID/email, device ID).
- Authorization errors due to invalid or insufficient API credentials.
- Validation errors if the user identifier type does not match the provided identifier.
Resolutions:
- Verify all required fields are correctly filled according to the chosen options.
- Ensure the API key has permissions for the specified WhatsApp number and team operations.
- When reassigning chats, confirm the target user exists and is valid.
Links and References
- Wassenger Official API Documentation (for detailed API usage and team management endpoints)
- n8n Documentation on Creating Custom Nodes