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
The "Create New Team" operation under the "Reseller" resource allows users to create a new team entity within a reseller context. This node is useful for automating team management workflows, such as onboarding new teams with specific configurations or integrating team creation into larger business processes. For example, a company managing multiple reseller accounts can automatically provision teams with predefined attributes like SKU tiers or external identifiers.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the new team to be created. |
| Additional Body Fields | Optional additional fields to customize the team creation request: |
| - External Id | An optional external identifier for the team. |
| - Microsoft Tenant Id | Optional Microsoft tenant ID associated with the team. |
| - Tier Sku | SKU of the product being added to this team (e.g., subscription tier or license type). |
| - Purchase Order | Optional purchase order number related to the team creation. |
Output
The node outputs JSON data representing the newly created team object as returned by the API. This typically includes details such as the team's unique ID, name, associated SKUs, and any other metadata provided by the service. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authentication to the backend service managing resellers and teams.
- The base URL for API requests is configured via credentials.
- The node depends on an OpenAPI-based client library (
@avantguardllc/n8n-openapi-node) for making HTTP requests.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the node will likely throw an error indicating a missing required parameter.
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions to create teams.
- Invalid SKU or Tenant ID: Providing invalid values in optional fields like "Tier Sku" or "Microsoft Tenant Id" may cause API errors; verify these values against your service provider's documentation.
- Network Issues: Connectivity problems to the API endpoint will result in request failures; check network settings and API availability.
Links and References
- No direct links are available from the source code. For more information, consult the API documentation of the reseller service you are integrating with or the n8n community forums for similar node usage examples.