Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
This node integrates with the OrderDesk API, allowing users to manage various resources such as orders, shipments, inventory items, and more. Specifically, for the Inventory Items - Create operation, it enables creating new inventory items in the OrderDesk system by sending custom JSON data representing the item details.
Common scenarios include automating inventory management workflows where new products or stock items need to be added programmatically from other systems or processes. For example, when a new product is added to an e-commerce platform, this node can create the corresponding inventory item in OrderDesk automatically.
Properties
| Name | Meaning |
|---|---|
| Post Data | The JSON-formatted data representing the inventory item to be created. This data structure varies based on the OrderDesk API specification. Users must provide valid JSON according to OrderDesk API docs. |
Output
The node outputs the response from the OrderDesk API after attempting to create the inventory item. The json output field contains the API's JSON response, which typically includes details of the newly created inventory item such as its ID, name, quantity, and other metadata.
If the API supports binary data (e.g., images or files related to inventory), the node would handle that accordingly, but based on the provided code and properties, the primary output is JSON data reflecting the created inventory item.
Dependencies
- Requires an active connection to the OrderDesk API.
- Users must configure an API authentication credential (an API key or token) within n8n to authorize requests.
- The base URL for API requests is
https://app.orderdesk.me. - The node sends requests with headers specifying JSON content type (
application/json).
Troubleshooting
- Invalid JSON in Post Data: If the JSON provided in the "Post Data" property is malformed, the API request will fail. Ensure the JSON is correctly formatted and matches the expected schema.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n credentials.
- API Endpoint Issues: If the resource or operation is not supported or the API endpoint changes, errors may occur. Confirm the resource and operation names match those supported by the OrderDesk API.
- Network Issues: Connectivity problems between n8n and the OrderDesk API server can cause timeouts or failed requests.
Links and References
- OrderDesk API Documentation
- OrderDesk Inventory API Reference (specific section for inventory items creation)