Actions16
- Orders Actions
- Shipments Actions
- Inventory Items Actions
- Move Orders Actions
Overview
The node integrates with the OrderDesk API, allowing users to manage various aspects of their OrderDesk account programmatically. Specifically, for the Orders - Create operation, it enables creating new orders by sending order data in JSON format to the OrderDesk system.
This node is beneficial in automation workflows where new orders need to be created dynamically based on external triggers or data sources, such as e-commerce platforms, CRM systems, or custom order management solutions.
Example use case: Automatically create a new order in OrderDesk when a customer places an order on a website or through another sales channel, by passing the order details as JSON to this node.
Properties
| Name | Meaning |
|---|---|
| Post Data | The JSON-formatted data representing the order to be created. This must conform to OrderDesk's API schema for creating orders. Users provide the full order details here. |
Output
The node outputs the response from the OrderDesk API after attempting to create the order. The json output field contains the API's JSON response, which typically includes details about the newly created order such as its ID, status, and any other metadata returned by OrderDesk.
If the API supports binary data (not indicated here), it would be included accordingly, but for this operation, the focus is on JSON responses.
Dependencies
- Requires an active connection to the OrderDesk API.
- Users must configure an API authentication credential (e.g., an API key) within n8n to authorize requests.
- The base URL used for requests is
https://app.orderdesk.me. - The node sends requests with headers specifying JSON content type and acceptance.
Troubleshooting
- Invalid JSON in Post Data: If the JSON provided in the "Post Data" property is malformed or does not match the expected schema, the API will likely return an error. Ensure the JSON is valid and follows OrderDesk's API documentation.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key or token is correctly configured in n8n.
- API Rate Limits or Downtime: If the OrderDesk API is unreachable or rate limits are exceeded, requests may fail. Check network connectivity and API status.
- Missing Required Fields: The API may reject the creation request if required order fields are missing. Consult the OrderDesk API docs to ensure all mandatory fields are included.
Links and References
- OrderDesk API Documentation — Detailed information on the JSON structure for creating orders and other operations.