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 updates an existing external team in a specified account. It is useful when you need to modify details of an external team, such as changing its name, members, or other attributes defined in the external team object. Typical use cases include synchronizing team information from another system, correcting team data, or automating team management workflows.
For example, if your organization manages teams externally and wants to keep the team data up-to-date in this system, you can use this node to push updates automatically whenever changes occur.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account where the external team exists. This is required to specify which account's team should be updated. |
| Body | JSON object representing the external team with updated fields. Should exclude autogenerated fields. This contains the new data for the external team. |
Output
The node outputs the response from the update operation in the json field of the output item. This typically includes the updated external team object reflecting the changes made. The exact structure depends on the API response but generally contains the team's properties after the update.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on the external service's API endpoint for managing external teams.
- The base URL for the API must be set in the node credentials or environment configuration.
Troubleshooting
- Missing or invalid Account Id: Ensure the Account Id is provided and correctly identifies an existing account; otherwise, the update will fail.
- Malformed JSON in Body: The Body property must be valid JSON without autogenerated fields. Invalid JSON will cause parsing errors.
- Authentication errors: Verify that the API key or authentication token is correctly configured and has permissions to update external teams.
- API errors: If the external service returns errors (e.g., team not found, validation errors), check the response message for details and adjust input accordingly.
Links and References
- Refer to the external service’s API documentation for the exact schema of the external team object and update operation.
- n8n documentation on using JSON input and configuring API credentials may help in setting up this node properly.