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 by sending the updated team data to an API. It is useful when you need to modify details of an external team, such as changing team attributes or metadata, without affecting autogenerated fields.
Practical examples include:
- Updating the name or description of an external team.
- Modifying team settings or custom properties stored in the external system.
- Synchronizing team information from another system by pushing updates programmatically.
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 with updated fields, excluding autogenerated ones. |
Output
The node outputs the response from the API after updating the external team. The json output field contains the updated external team object as returned by the API, reflecting the changes made.
If the API supports binary data in responses, it would typically relate to attachments or files associated with the team, but this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing teams.
- Needs the base URL of the API configured in credentials or environment variables.
- Depends on the external API supporting update operations on external teams via HTTP PATCH or PUT methods.
Troubleshooting
- Invalid Account Id: If the provided account identifier does not exist or is incorrect, the API may return a 404 Not Found error. Verify the account ID is correct.
- Malformed JSON Body: Providing invalid JSON in the "Body" property will cause parsing errors. Ensure the JSON is well-formed and matches the expected schema without autogenerated fields.
- Authentication Errors: Missing or invalid API credentials will result in authentication failures. Confirm that the API key or token is correctly set up.
- Permission Denied: Insufficient permissions to update external teams can cause authorization errors. Check user roles and API scopes.
- API Rate Limits: Frequent updates might hit rate limits imposed by the API. Implement retry logic or reduce request frequency if needed.
Links and References
- Refer to the external team's API documentation for detailed schema and update operation specifics.
- Consult your API provider’s authentication guide to properly configure credentials.
- JSON formatting tools can help validate the "Body" input before use.