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
- Cards Actions
- Suppliers Actions
- Fund Accounts 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 supplier in a specified account. It is useful when you need to modify supplier details such as contact information, status, or other attributes maintained by the external system managing suppliers. Typical use cases include synchronizing supplier data from another system, correcting supplier records, or automating supplier management workflows.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account where the supplier exists. This is required to specify the context for the update operation. |
| Supplier Id | Identifier of the supplier to be updated. This uniquely identifies which supplier record will be modified. |
Output
The node outputs JSON data representing the updated supplier object returned from the external API after the update operation completes successfully. The structure typically includes the supplier's updated fields and metadata confirming the changes.
If the node supports binary data output (not evident from the provided code), it would represent any file or media associated with the supplier update, but no such indication is present here.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external supplier management service.
- Depends on the external API endpoint that manages supplier data; the base URL and headers are set via credentials.
- Uses an OpenAPI-based client internally to perform the update operation.
Troubleshooting
- Missing Required Fields: Errors may occur if "Account Id" or "Supplier Id" are not provided or invalid. Ensure these IDs are correct and exist in the target system.
- Authentication Failures: If the API key or authentication token is missing or expired, the node will fail to connect. Verify credentials configuration.
- API Endpoint Issues: Network errors or incorrect base URLs can cause failures. Confirm the external service is reachable and the base URL is correctly set.
- Invalid Supplier Data: If the update payload contains invalid or unsupported fields, the API might reject the request. Validate input data before running the node.
Links and References
- Refer to the external supplier management API documentation for detailed information on supplier update endpoints and required fields.
- n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.