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 a specific item within a purchase order in an external system. It allows users to modify details such as the description, quantity, unit price, units of measurement, expense category, custom fields, and amortization information for a purchase order item. This is useful in scenarios where purchase orders need adjustments after creation, such as correcting quantities, updating pricing, or adding additional metadata.
Practical examples include:
- Correcting the quantity or unit price of an item after an initial order submission.
- Adding or updating expense categories or custom fields for better financial tracking.
- Adjusting amortization details related to the purchase order item.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the purchase order. |
| Purchase Order Id | Identifier of the purchase order containing the item to update. |
| Purchase Order Item Id | Identifier of the specific purchase order item to update. |
| Description | User-friendly description of the purchase order item. |
| Units | Unit of the purchase order item; options are "Pieces" or "Hours". |
| Purchased Quantity | Quantity of the purchase order item. |
| Unit Price | Price per unit of the purchase order item. |
| Expense Category | JSON object representing the expense category of the purchase order item. |
| Expense Custom Fields | JSON array representing custom fields associated with the purchase order item. |
| Amortization | JSON object containing amortization information related to the purchase order item. |
Output
The node outputs JSON data representing the updated purchase order item. This typically includes all the fields sent in the update request along with any additional metadata returned by the external API confirming the update. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external purchase order management system.
- The node uses HTTP requests with JSON payloads to interact with the external API.
- Proper configuration of the base URL and authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Missing or incorrect identifiers (Account Id, Purchase Order Id, Purchase Order Item Id) will cause the update to fail.
- Invalid JSON format in fields like Expense Category, Expense Custom Fields, or Amortization can lead to parsing errors.
- Insufficient permissions or expired API keys may result in authorization errors.
Error messages and resolutions:
- "Not Found" or similar errors usually indicate that one of the provided IDs does not exist or is incorrect.
- "Invalid JSON" errors suggest malformed JSON input in the respective fields; ensure valid JSON syntax.
- "Unauthorized" or "Forbidden" errors mean the API key or credentials are missing, invalid, or lack required permissions; verify and update credentials accordingly.
Links and References
- Refer to the external purchase order system's API documentation for detailed schema and field descriptions.
- JSON validation tools can help ensure correct formatting of JSON input fields before execution.