Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 an account in the target system. It is useful for organizing users or resources into hierarchical groups, facilitating management and access control. For example, you might use this node to programmatically add teams when onboarding new departments or projects, ensuring consistent structure without manual setup.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account under which the 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, allowing creation of nested team hierarchies. |
Output
The node outputs JSON data representing the newly created team object as returned by the API. This typically includes the team's unique ID, name, associated account ID, external ID if provided, parent ID if set, and possibly metadata such as creation timestamps. The output does not include binary data.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests.
- Depends on connectivity to the external service's API endpoint specified in the node credentials.
- The base URL and authentication details must be correctly set up in the node credentials for successful operation.
Troubleshooting
- Missing Required Fields: If "Account Id" is not provided, the node will fail because it is mandatory.
- Authentication Errors: Ensure that the API key or authentication token is valid and has permissions to create teams.
- Invalid Parent Id: Providing a non-existent parent team ID may cause errors; verify the parent ID exists before use.
- API Connectivity Issues: Network problems or incorrect base URL configuration can prevent the node from reaching the API.
- Duplicate External Ids: If the external ID must be unique, reusing one may cause conflicts or errors.
Links and References
- Refer to the external service’s API documentation for detailed information about the team creation endpoint and required fields.
- Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.