Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
The node integrates with the OrderDesk API to update inventory items. It allows users to modify existing inventory records by specifying the inventory item's unique identifier and providing updated data in JSON format. This is useful for synchronizing inventory details such as stock levels, pricing, or product attributes between OrderDesk and other systems.
Practical examples include:
- Automatically updating stock quantities after sales or restocking.
- Changing product descriptions or metadata based on external inputs.
- Adjusting pricing or availability dynamically from an ERP or inventory management system.
Properties
| Name | Meaning |
|---|---|
| Inventory ID | The unique identifier of the inventory item to update. Required to specify which item to modify. |
| Post Data | The JSON-formatted data containing the fields and values to update for the specified inventory item. The structure varies depending on the API's requirements. |
Output
The node outputs JSON data representing the response from the OrderDesk API after attempting to update the inventory item. This typically includes confirmation of the update, the updated inventory item details, or error information if the update failed.
No binary data output is indicated.
Dependencies
- Requires an active connection to the OrderDesk API.
- Needs a valid API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://app.orderdesk.me. - The node sends and expects JSON content type headers.
Troubleshooting
- Invalid Inventory ID: If the provided Inventory ID does not exist or is incorrect, the API will likely return an error indicating the item was not found. Verify the ID before running the node.
- Malformed JSON in Post Data: Ensure that the JSON provided in the Post Data property is correctly formatted and matches the expected schema for the inventory update endpoint.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Confirm that the API key/token is correctly set up in n8n.
- API Rate Limits or Downtime: Temporary issues with the OrderDesk API may result in errors or timeouts. Retrying after some time or checking API status can help.
- Required Fields Missing: Some updates may require certain mandatory fields in the Post Data. Consult the OrderDesk API documentation to ensure all required data is included.