Actions33
- Public Actions
- Public Admin Actions
- Reseller Actions
- Create New Team
- Get Team Information
- Update Team
- Remove Team From Reseller
- Update Team Avatar
- Create Team Bulk Inboxes And Users
- Get Team Users
- Add User To Team
- Remove Users From Team
- Get Team Inboxes
- Remove Team Inboxes
- Create Team Bulk Inboxes
- Assign Users To Inbox
- Remove Users From Inbox
- Get Team Whitelist Domains
- Create Team Whitelisted Domain
- Remove Team Whitelisted Domain
- Create Reseller
- Import Team Users
- Get Import Team Users Job Status
Overview
This node integrates with the AvantGuard ClerkChat service, specifically providing an operation to remove a user from the Clerk Chat system. It is useful in scenarios where administrators need to manage chat users by deleting those who are no longer active or authorized. For example, if a user leaves an organization or should be blocked from accessing the chat, this node can be used to remove their user record by specifying their unique ID.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the user to remove from Clerk Chat. This is a required string input. |
Output
The node outputs JSON data representing the result of the removal operation. Typically, this would include confirmation of successful deletion or details about any errors encountered. The exact structure depends on the API response but generally confirms whether the user was removed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard ClerkChat API.
- The base URL for the API is configured via credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
Common issues:
- Providing an invalid or non-existent user ID will likely cause the API to return an error indicating the user could not be found.
- Missing or incorrect API authentication credentials will result in authorization errors.
- Network connectivity problems may prevent the node from reaching the ClerkChat API.
Error messages:
- "User not found" or similar indicates the specified ID does not exist; verify the ID before retrying.
- Authentication errors suggest checking the API key or token configuration.
- Timeout or connection errors require verifying network access and API endpoint availability.
Links and References
- AvantGuard ClerkChat API documentation (not provided here, but typically available from AvantGuard).
- n8n documentation on creating and using custom nodes with API integrations.