Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
The node interacts with the OrderDesk API, specifically allowing operations on various resources including Inventory Items. For the "Inventory Items" resource, the "Get" operation retrieves details about a specific inventory item by its unique Inventory ID. This is useful for scenarios where you need to fetch current stock information, verify product details, or synchronize inventory data between OrderDesk and other systems.
Practical examples:
- Fetching an inventory item's details before updating stock levels.
- Retrieving product information to display in a custom dashboard.
- Validating that an inventory item exists before processing orders.
Properties
| Name | Meaning |
|---|---|
| Inventory ID | The unique identifier of the inventory item to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the inventory item retrieved from OrderDesk. The structure typically includes fields such as item identifiers, quantities, descriptions, pricing, and other relevant inventory metadata as provided by the OrderDesk API.
If the node supports binary data output (not indicated here), it would represent associated files or media related to the inventory item, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the OrderDesk API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://app.orderdesk.me. - The node expects JSON responses and sends JSON-formatted requests.
Troubleshooting
- Missing or invalid Inventory ID: Since Inventory ID is required, ensure it is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key or token credential is correctly set up and has sufficient permissions.
- Network issues: Check connectivity to
https://app.orderdesk.meand firewall settings. - API rate limits or downtime: If requests fail repeatedly, confirm if OrderDesk API is operational and within usage limits.
- Unexpected response structure: If the output JSON does not match expectations, verify the Inventory ID exists and the API version compatibility.
Links and References
- OrderDesk API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating and using API credentials