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
External Teams → Update External Teams
AI-generatedOverview
This node allows you to update external teams within an account by sending a JSON object representing the external team data. It is useful in scenarios where you need to modify team details programmatically, such as updating team names, members, or other attributes managed externally. For example, you might use this node to synchronize team information from another system into your platform or to automate updates based on workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account where the external team exists and will be updated (string). |
| Body | JSON object representing the external team data to update, excluding autogenerated fields. |
Output
The node outputs JSON data reflecting the response from the update operation. This typically includes the updated external team object or confirmation of the update. The output does not explicitly mention binary data, so it is assumed to be purely JSON.
Dependencies
- Requires an API key credential for authentication with the external service.
- Needs the base URL of the API configured in credentials.
- Depends on the external API endpoint that manages external teams.
Troubleshooting
- Invalid Account Id: If the provided account identifier is incorrect or does not exist, the API may return an error indicating the resource was not found. Verify the account ID before running the node.
- Malformed JSON Body: The "Body" property must be valid JSON without autogenerated fields. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
- Authentication Errors: Missing or invalid API credentials will result in authorization failures. Ensure the API key or token is correctly set up in n8n credentials.
- API Endpoint Issues: Network problems or changes in the external API can cause failures. Check connectivity and API documentation if unexpected errors occur.
Links and References
- Refer to the external API documentation for details on the external team object structure and update semantics.
- n8n documentation on using JSON input properties and API credentials configuration.