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 in scenarios where team details such as the team name, external system identifier, or parent team need to be modified after creation. For example, if a team's name changes due to reorganization or if you want to link the team to a different parent team, this operation allows you to update those details programmatically.
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 an external system (useful for integration purposes). |
| Parent Id | Unique identifier of the parent team, allowing hierarchical structuring of teams. |
Output
The output JSON contains the updated team information reflecting the changes made by this operation. This typically includes the team’s identifiers and any updated fields such as name, external ID, and parent ID. The node does not output binary data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on connectivity to the external service managing groups and teams (the Zitadel API as indicated by the bundled code).
- The base URL for the API must be set in the node credentials or environment variables.
Troubleshooting
- Missing Required Fields: Errors may occur if "Group Id" or "Team Id" are not provided. Ensure these mandatory fields are filled.
- Invalid Identifiers: Providing incorrect or non-existent group or team IDs will result in errors from the API indicating resource not found.
- Authentication Failures: If the API key or authentication token is missing or invalid, the node will fail with authorization errors.
- Network Issues: Connectivity problems to the external API endpoint can cause timeouts or request failures.
- To resolve these issues, verify all required inputs, confirm valid credentials, and ensure network access to the API endpoint.
Links and References
- Zitadel API Documentation (assumed based on bundled code context)
- n8n documentation on Creating Custom Nodes