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 an account. It is useful in scenarios where team details such as the team name, external system identifier, or hierarchical parent relationship need to be modified after creation. For example, you might use this node to rename a team, link it to an external system's ID for synchronization purposes, or reorganize teams by changing their parent team.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the team belongs (required). |
| Team Id | Identifier of the team to update (required). |
| Name | New name of the team. |
| External Id | Unique identifier of the team in an external system, useful for integration and mapping. |
| Parent Id | Unique identifier of the parent team, allowing hierarchical structuring of teams. |
Output
The node outputs JSON data representing the updated team information as returned by the API. This typically includes the team's identifiers and any updated fields such as name, external ID, and parent ID. The output can be used downstream in workflows to confirm the update or trigger further actions.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing accounts and teams.
- The base URL for the API must be configured in the node credentials.
- The node depends on an OpenAPI-based client library for making HTTP requests to the API.
Troubleshooting
- Missing Required Fields: If "Account Id" or "Team Id" are not provided, the node will fail because these are essential to identify which team to update.
- Invalid Identifiers: Providing incorrect or non-existent account or team IDs will result in errors from the API indicating that the resource was not found.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update team information.
- Network Issues: Connectivity problems with the API endpoint will cause request failures; verify network access and base URL configuration.
- Validation Errors: If the new values for fields like "Name" or "External Id" do not meet API validation rules, the API will return descriptive error messages.
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 using API key credentials and configuring HTTP request nodes may help set up authentication correctly.