Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
This node integrates with the OrderDesk API to list inventory items based on specified filter criteria. It is useful for workflows that need to retrieve and process inventory data from an OrderDesk store, such as syncing stock levels, generating reports, or automating inventory management tasks.
For example, you can use this node to fetch all inventory items matching certain attributes (like SKU or category) by specifying query parameters as filters. This allows downstream nodes in your workflow to act on a filtered subset of inventory data.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only "Query" (query parameters) is supported. |
| Filter criteria | Key/value pairs used as query parameters to filter the inventory items returned by the API. |
The Filter criteria property allows multiple key-value pairs to be defined, where each key is the name of a query parameter and the value is its corresponding filter value. These are sent as URL query parameters to the API endpoint.
Output
The node outputs JSON data representing the list of inventory items retrieved from the OrderDesk API. The structure typically includes an array of inventory item objects, each containing details such as SKU, quantity, price, and other relevant fields as provided by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for OrderDesk to authorize requests.
- Connects to the OrderDesk API at
https://app.orderdesk.me. - The node expects the user to configure appropriate credentials within n8n to access the API.
Troubleshooting
- Empty or no results: Ensure that the filter criteria keys and values match valid query parameters supported by the OrderDesk API. Incorrect keys or values may result in empty responses.
- Authentication errors: Verify that the API authentication token is correctly configured and has sufficient permissions.
- Network or API errors: Check network connectivity and confirm the OrderDesk API service status.
- Invalid property configuration: Make sure the "Type of Data" is set to "Query" and that filter criteria are properly formatted as key-value pairs.
Links and References
- OrderDesk API Documentation (for detailed information on available query parameters and response structure)