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 purchase orders from an external system. It allows users to query purchase orders with flexible filtering, pagination (skip and take), and requires specifying the account identifier. This is useful in scenarios where you want to automate workflows involving purchase order management, such as syncing purchase orders into a CRM, generating reports, or triggering actions based on purchase order data.
Practical examples:
- Fetching all purchase orders for a specific account that meet certain status criteria.
- Paginating through large sets of purchase orders to process them in batches.
- Filtering purchase orders modified after a certain date to update downstream systems.
Properties
| Name | Meaning |
|---|---|
| Filter | JSON-stringified and URL-encoded filter expression object conforming to a purchase order filter schema. Allows complex queries on fields like status, purchaseOrderNumber, modifiedAt, and logical AND conditions. |
| Skip | Number of purchase order objects to skip from the beginning of the result set. Useful for pagination. |
| Take | Maximum number of purchase order objects to return. Default is 20; maximum allowed is 1000. Controls page size. |
| Account Id | Identifier of the account whose purchase orders are being queried. This is required to scope the request. |
Output
The output contains a JSON array of purchase order objects matching the specified filters and pagination parameters. Each object represents a purchase order with its associated data fields as returned by the external API.
No binary data output is indicated.
Dependencies
- Requires connection to an external API service managing purchase orders.
- Needs an API base URL and authentication credentials configured in n8n (e.g., an API key or token).
- The node sends HTTP requests with query parameters constructed from the input properties.
Troubleshooting
- Empty results: Check that the
Account Idis correct and that the filter expression matches existing purchase orders. - Invalid filter JSON: Ensure the filter property is a valid JSON string and properly URL-encoded.
- Pagination issues: If no results appear when using
SkipandTake, verify these values are within the range of available data. - Authentication errors: Confirm that the API credentials are correctly set up and have sufficient permissions.
- API rate limits: Large
Takevalues or frequent calls may hit API limits; reduce batch sizes or add delays.
Links and References
- Refer to the external API documentation for the purchase order resource and filter schema.
- n8n documentation on HTTP Request nodes and pagination best practices.