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 operation, Create Team Bulk Inboxes, allows users to create multiple inboxes in bulk for a specified team within a reseller context. It is useful when managing communication channels or support inboxes for teams at scale, enabling efficient onboarding or updating of many inboxes simultaneously.
Practical scenarios include:
- A reseller setting up multiple customer support inboxes for a new team.
- Automating the creation of several inboxes after team formation without manual entry.
- Bulk importing inbox configurations from external systems into the platform.
Properties
| Name | Meaning |
|---|---|
| Team Id | The unique identifier of the team for which the inboxes will be created (string). |
| Inboxes | A JSON array containing data objects for each reseller inbox to be created in bulk. |
The Inboxes property expects a JSON array where each element represents an inbox's configuration details. This allows flexible and complex inbox definitions to be passed in one request.
Output
The node outputs JSON data representing the result of the bulk inbox creation operation. Typically, this would include confirmation of created inboxes, their assigned IDs, statuses, or any error messages related to individual inbox creations.
If binary data were involved (not indicated here), it would represent files or attachments related to inboxes, but this node focuses on JSON structured data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard ClerkChat service.
- Depends on the external AvantGuard ClerkChat API endpoint configured via credentials.
- Uses the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled internally for request building and validation.
Troubleshooting
- Invalid Team Id: If the provided team ID does not exist or is malformed, the API may return an error. Verify the team ID before running the node.
- Malformed Inboxes JSON: The inboxes input must be valid JSON. Parsing errors will cause the node to fail. Use proper JSON formatting and validate the structure.
- Authentication Errors: Missing or invalid API credentials will prevent successful requests. Ensure the API key credential is correctly set up.
- Partial Failures: Some inboxes might fail creation due to validation issues while others succeed. Check the output response for detailed error messages per inbox.
Links and References
- AvantGuard ClerkChat API Documentation (example placeholder link)
- n8n documentation on Using JSON Input
- General best practices for Bulk Data Operations