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 operation retrieves a list of items associated with a specific purchase order within an account. It is useful in scenarios where you need to fetch detailed line items or components that make up a particular purchase order, such as for auditing, reporting, or integration with other systems like inventory or accounting software.
Practical examples include:
- Extracting all products or services ordered under a given purchase order to update stock levels.
- Generating detailed invoices or shipment documents based on the purchase order items.
- Synchronizing purchase order details with external ERP or financial systems.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the purchase order belongs. |
| Purchase Order Id | Identifier of the specific purchase order whose items are to be retrieved. |
Output
The output will contain a JSON array representing the list of items for the specified purchase order. Each item typically includes details such as product identifiers, quantities, descriptions, prices, and other relevant metadata depending on the API's response structure.
If the node supports binary data output (not indicated here), it would generally represent attachments or files related to the purchase order items, but this operation focuses on JSON data retrieval.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service managing purchase orders.
- The node depends on a REST API endpoint that provides purchase order item data.
- Proper configuration of the base URL and authentication headers is necessary for successful API communication.
Troubleshooting
- Missing or invalid Account Id or Purchase Order Id: Ensure these required fields are correctly set; otherwise, the API may return errors or empty results.
- Authentication errors: Verify that the API key or authentication credentials are valid and have sufficient permissions to access purchase order data.
- Network or connectivity issues: Check network settings and API availability if requests time out or fail.
- Unexpected API responses: If the API changes or returns unexpected data structures, the node might not parse the output correctly. Review API documentation and update the node configuration accordingly.
Links and References
- Refer to the external API documentation for purchase orders and their items for detailed field definitions and usage guidelines.
- n8n documentation on creating and configuring HTTP request nodes and handling API credentials.