Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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 purchase order in a system that manages purchase orders. It allows users to modify details such as the account associated with the purchase order, the purchase order identifier, notes from the creator, supplier information, and the currency used.
Common scenarios for this node include:
- Correcting or adding additional information to a purchase order after it has been created.
- Updating supplier details or notes based on new information.
- Changing the currency of the purchase order if needed.
Practical example:
A finance team member realizes that the supplier information on a purchase order was entered incorrectly. They can use this node to update the supplier JSON data without needing to recreate the entire purchase order.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the purchase order (required). |
| Purchase Order Id | Identifier of the purchase order to update (required). |
| Note | A textual note from the creator of the purchase order, providing additional context. |
| Supplier | JSON object representing the expense category or supplier details related to the order. |
| Currency | Currency code for the purchase order. Options include AED, USD, EUR, GBP, JPY, and many others (see full list in properties). |
Output
The node outputs JSON data representing the updated purchase order. This typically includes all fields of the purchase order after the update operation, reflecting any changes made through the input properties.
If the node supports binary data output, it is not indicated here; thus, the output is primarily JSON structured data.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to connect to the external purchase order management API.
- The base URL for the API must be set in the node's credential configuration.
- The node uses standard HTTP headers for JSON content (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Missing Required Fields: Errors may occur if "Account Id" or "Purchase Order Id" are not provided. Ensure these required fields are filled.
- Invalid JSON in Supplier Field: Since the supplier property expects JSON, invalid JSON syntax will cause errors. Validate JSON format before input.
- Unsupported Currency Code: Using a currency code not listed in the options may result in rejection by the API.
- Authentication Failures: If the API key or authentication token is missing or incorrect, the node will fail to update the purchase order. Verify credentials and API access.
- Network or API Errors: Timeouts or server errors from the external API should be handled by retrying or checking API status.
Links and References
- Refer to your purchase order management system’s API documentation for detailed information on the update purchase order endpoint.
- Currency codes follow ISO 4217 standards; see https://www.iso.org/iso-4217-currency-codes.html for reference.