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 allows users to create a new purchase order item within a specified purchase order. It is useful in scenarios where you need to programmatically add detailed line items to purchase orders, such as when automating procurement workflows or integrating with accounting systems.
For example, if your company uses an external system to manage purchase orders, this node can be used to add individual items specifying quantities, pricing, and expense categories directly from n8n workflows, streamlining the purchasing process.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the purchase order item. |
| Purchase Order Id | Identifier of the purchase order to which the item will be added. |
| Units | Unit of measurement for the purchase order item. Options: Pieces, Hours. |
| Expense Category | JSON object describing the expense category of the purchase order item. |
| Expense Custom Fields | JSON array defining custom fields related to the expense for the purchase order item. |
| Amortization | JSON object containing amortization information for the purchase order item. |
| Description | User-friendly description of the purchase order item. |
| Purchased Quantity | Number representing the quantity of the purchase order item. |
| Unit Price | Number representing the price per unit of the purchase order item. |
Output
The node outputs a JSON object representing the newly created purchase order item. This typically includes all details sent in the request along with any additional metadata or identifiers assigned by the backend service.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- The node interacts with an external API endpoint (base URL configurable via credentials) that manages purchase orders.
- Proper network connectivity and valid credentials are necessary for successful execution.
Troubleshooting
- Missing Required Fields: Errors may occur if required properties like Account Id, Purchase Order Id, Description, Purchased Quantity, or Unit Price are not provided. Ensure all mandatory fields are filled.
- Invalid JSON Format: Properties like Expense Category, Expense Custom Fields, and Amortization expect valid JSON strings. Malformed JSON will cause parsing errors.
- Authentication Failures: If the API key or authentication token is invalid or missing, the node will fail to connect. Verify credentials configuration.
- API Endpoint Issues: Network issues or incorrect base URL settings can prevent communication with the external service.
- Data Validation Errors: Providing unsupported units or invalid numeric values might result in API rejections.
Links and References
- No direct links available from the source code. For more information, consult the documentation of the external purchase order management API integrated with this node.