Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation allows you to create a new team within a specified group. It is useful in scenarios where you need to organize users or resources into hierarchical teams under a group structure, such as managing departments within an organization or project teams within a larger group.
Practical examples include:
- Creating a new project team inside a department group.
- Adding a sub-team under an existing parent team for better organizational clarity.
- Synchronizing external system team structures by creating corresponding teams in the target system.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group under which the new team will be created. (Required) |
| Name | Name of the Team to be created. |
| External Id | Unique identifier of the Team in an external system, useful for synchronization purposes. |
| Parent Id | Unique identifier of the parent team, if this team is a sub-team under another team. |
Output
The output JSON contains the details of the newly created team as returned by the API. This typically includes the team's unique identifiers, name, and any other metadata provided by the service after creation.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service managing groups and teams.
- The node uses a base URL and headers preset for JSON communication with the API.
- The external service must support creating teams via an HTTP POST request with the provided properties.
Troubleshooting
- Missing Required Fields: If "Group Id" is not provided, the node will likely fail because it cannot determine where to create the team.
- Authentication Errors: Ensure that the API key or authentication token is correctly set up in n8n credentials; otherwise, the API will reject the request.
- Invalid Parent Id: Providing a non-existent or incorrect "Parent Id" may cause the API to return an error.
- API Endpoint Issues: Network issues or incorrect base URL configuration can prevent successful communication with the API.
Links and References
- Refer to the external API documentation for detailed information on team creation endpoints and required fields.
- n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.