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 updates information about a specific team within an account. It is useful in scenarios where team details such as the team’s name, external system identifier, or hierarchical parent need to be modified after creation. For example, if a team changes its name or is reorganized under a different parent team, this operation allows you to keep the data synchronized with your external system.
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 for the team. |
| External Id | Unique identifier of the team in the external system, useful for cross-system 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 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 for authentication with the external service.
- The node uses a base URL configured in the credentials to send HTTP requests.
- The underlying implementation depends on an OpenAPI specification for request construction and response parsing.
Troubleshooting
- Missing Required Fields: If
Account IdorTeam Idare not provided, the operation will fail. Ensure these identifiers are correctly set. - Invalid Identifiers: Providing incorrect or non-existent account or team IDs may result in errors from the API indicating that the resource was not found.
- Permission Issues: Insufficient permissions associated with the API key can cause authorization errors.
- Network Errors: Connectivity issues or incorrect base URL configuration can prevent successful API calls.
- Empty Update: Sending no fields to update (only required IDs) might result in no changes or an error depending on the API behavior.
Links and References
- Refer to the external service’s API documentation for detailed information on team management endpoints.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.