Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
The node integrates with the OrderDesk API to update existing orders. It allows users to modify order details by specifying the order ID and providing updated data in JSON format. This is useful for automating order management workflows, such as correcting order information, updating shipping details, or changing order statuses programmatically.
Practical examples include:
- Automatically updating an order's shipping address after receiving customer changes.
- Modifying order items or quantities based on inventory availability.
- Adjusting order metadata or custom fields before fulfillment.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to update. Required to specify which order will be modified. |
| Post Data | JSON-formatted data containing the fields and values to update on the specified order. The structure varies depending on the update action per OrderDesk API documentation. |
Output
The node outputs JSON data representing the response from the OrderDesk API after attempting to update the order. This typically includes the updated order details or confirmation of the successful update. If the API returns errors, those will also be included in the output JSON.
The node does not output binary data.
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 receives data in JSON format with appropriate headers (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid Order ID: If the provided Order ID does not exist, the API will return an error. Verify the Order ID is correct.
- Malformed JSON in Post Data: Ensure that the JSON provided in the Post Data property is well-formed and matches the expected schema for the update operation.
- Authentication Errors: If the API key or token is missing or invalid, the request will fail. Confirm that the API credentials are correctly set up in n8n.
- API Rate Limits or Downtime: Temporary failures may occur due to rate limiting or service outages. Retry after some time or check OrderDesk status.
- Missing Required Fields: Some updates may require specific fields in the JSON payload; consult the OrderDesk API docs to ensure all required data is included.
Links and References
- OrderDesk API Documentation — Detailed reference for the JSON structure and available update operations.