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 API to assign multiple users to a specific inbox within a team. It is useful in scenarios where an organization wants to manage user access and collaboration by grouping users under shared inboxes for handling communications or tasks collectively. For example, a support team lead can assign several support agents to a common inbox to streamline customer inquiries.
Properties
| Name | Meaning |
|---|---|
| Team Id | The unique identifier of the team to which the inbox belongs. |
| Inbox Id | The unique identifier of the inbox where users will be assigned. |
| User Ids | A JSON array containing the IDs of users to be assigned to the specified inbox. |
Output
The node outputs JSON data representing the result of the assignment operation. This typically includes confirmation details such as success status or updated inbox-user mappings. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard ClerkChat service.
- The base URL for the API is configured via node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and the bundled OpenAPI specification (openapi.json) for request construction.
Troubleshooting
- Invalid or missing Team Id / Inbox Id: Ensure these IDs are correct and exist in the AvantGuard system; otherwise, the API may return errors indicating resource not found.
- Malformed User Ids JSON: The
User Idsproperty must be a valid JSON array. Invalid JSON will cause parsing errors before the API call. - Authentication failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- API connectivity issues: Check network connectivity and the correctness of the API base URL in credentials.
Links and References
- AvantGuard ClerkChat API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes