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 updates information about a specific team within a group. It is useful when you need to modify team details such as the team's name, external identifier, or its parent team relationship in an organizational structure managed via an external system. Practical examples include renaming a team after restructuring, linking a team to a new parent team, or synchronizing team identifiers with an external database.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group to which the team belongs. |
| Team Id | Identifier of the team to update. |
| Name | New name for the team. |
| External Id | Unique identifier of the team in the external system. |
| Parent Id | Unique identifier of the parent team, establishing hierarchical relationships. |
Output
The node outputs JSON data representing the updated team information as returned by the external API. This typically includes the updated fields such as the team’s name, external ID, parent ID, and any other metadata provided by the service. The output does not include binary data.
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 HTTP requests with JSON payloads to communicate with the external API.
- Proper base URL configuration for the API endpoint is necessary in the node credentials or settings.
Troubleshooting
- Missing Required Fields: Errors may occur if "Group Id" or "Team Id" are not provided. Ensure these mandatory fields are filled.
- Authentication Failures: If the API key or authentication token is invalid or missing, the node will fail to update the team. Verify credentials are correctly set up.
- Invalid Identifiers: Providing non-existent group or team IDs will result in errors from the external API. Confirm that IDs are correct.
- API Response Errors: Network issues or API downtime can cause failures. Check connectivity and API status.
- Field Validation: Some fields like "Name" or "External Id" might have format restrictions enforced by the API; ensure values comply with those rules.
Links and References
- Refer to the external API documentation for detailed information on the team update endpoint, including field constraints and response formats.
- n8n documentation on how to configure API credentials and use HTTP request nodes may be helpful for setup.