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 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 output JSON contains the updated team information as returned by the API after the update operation. This typically includes the team’s identifiers and any fields that were changed or confirmed. The node does not output binary data.
Dependencies
- Requires an API key credential for authentication with the external service.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external API described by the bundled OpenAPI specification (
payhawk.api.json).
Troubleshooting
- Missing Required Fields: If
Account IdorTeam Idare not provided, the operation will fail. Ensure these are set correctly. - Invalid Identifiers: Providing incorrect or non-existent account or team IDs may result in errors from the API indicating resource not found.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update team information.
- Network Issues: Connectivity problems can cause timeouts or failed requests; verify network access to the API endpoint.
- Validation Errors: If the new values (e.g.,
Name,External Id) do not meet the API’s validation rules, the request will be rejected with descriptive error messages.
Links and References
- Refer to the external API documentation for detailed field constraints and examples.
- n8n documentation on how to configure API credentials and use HTTP-based nodes.