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
Team → Revoke Device Access
AI-generatedOverview
This node interacts with the WaliChat WhatsApp API to manage team-related operations, specifically focusing on revoking a user's access to a device (WhatsApp number) within a team. It allows administrators to revoke device access for a user identified either by their user ID or email. Additionally, it provides options to handle chats assigned to that user by unassigning, reassigning to another user, or resolving them. There is also an option to remove the user completely from the system.
Common scenarios where this node is beneficial:
- When a team member leaves or changes roles and should no longer have access to a specific WhatsApp device.
- To maintain security by promptly revoking access when needed.
- Managing chat assignments efficiently during user transitions by reassigning or resolving chats.
- Cleaning up user records by optionally removing users entirely.
Practical example:
An admin wants to revoke access of a user identified by email from a WhatsApp number device. They want all chats assigned to that user to be reassigned to another active team member. This node can perform that operation in one step, ensuring smooth transition and continued chat management.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which to revoke user access. |
| User Identifier Type | The type of identifier used to specify the user whose access will be revoked. Options: User ID or Email. |
| User ID | The unique 24-character hexadecimal ID of the user to revoke access from. Required if "User Identifier Type" is set to User ID. |
The email address of the user to revoke access from. Required if "User Identifier Type" is set to Email. |
|
| Action | The action to perform on chats assigned to the user being revoked. Options: Unassign Chats, Reassign Chats, Resolve Chats. |
| Reassign To User ID | The user ID to whom chats should be reassigned if the "Action" is set to Reassign Chats. This list depends on the selected WhatsApp number device. |
| Remove Completely | 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 details about the user access revocation and any chat reassignment or resolution actions performed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API.
- The node relies on the WaliChat API endpoints related to team management and device access control.
- Proper configuration of the API key credential in n8n is necessary.
- The node dynamically loads options such as available devices and team agents for selection.
Troubleshooting
Common issues:
- Providing an invalid or non-existent user ID or email may cause errors.
- Selecting a "Reassign Chats" action without specifying a valid reassignment user ID will likely fail.
- Revoking access from a user who does not currently have access to the specified device may return an error or no effect.
- Insufficient permissions or invalid API key credentials can cause authentication failures.
Error messages and resolutions:
- "User not found" — Verify the user identifier (ID or email) is correct and exists in the system.
- "Device not found" — Ensure the WhatsApp number/device ID is valid and accessible.
- "Invalid reassignment user" — When reassigning chats, confirm the target user ID is valid and belongs to the same device/team.
- Authentication errors — Check that the API key credential is correctly configured and has required permissions.
Links and References
- WaliChat Official API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General WhatsApp Business API concepts for team and device management
If you need further details on other operations or resources, feel free to ask!