Actions21
- Orders Actions
- Products Actions
- Repairs Actions
- Customers Actions
Overview
The node interacts with the Livo API to retrieve detailed information about orders. Specifically, the "Get Order Detail" operation fetches comprehensive data for a single order identified by its Order ID. This is useful in scenarios where you need to access full order details such as customer info, items ordered, status, and timestamps for further processing or reporting.
Practical examples:
- Fetching an order's details to display in a custom dashboard.
- Retrieving order information to trigger downstream workflows like shipping or invoicing.
- Auditing or verifying order contents before processing payments or refunds.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to retrieve details for. |
| Page Size | Number of transactions to return per page (used for pagination; applicable in some ops). |
| Current Page | The current page number for paginated results (applicable in some operations). |
| Start Date | Filter orders starting from this date (optional). |
| End Date | Filter orders up to this date (optional). |
For the "Get Order Detail" operation, only Order ID is required and used directly. The other properties are available but mainly relevant for list retrieval operations.
Output
The output JSON contains the full details of the requested order as returned by the Livo API endpoint /api/order?Id={orderId}. This typically includes:
- Order metadata (ID, status, dates)
- Customer information linked to the order
- List of products/items in the order with quantities and prices
- Payment and delivery details if available
- Any tags or notes associated with the order
The node outputs this data as a JSON object under the json field of the item. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Livo API.
- The node expects the base environment URL and API key to be configured in credentials.
- HTTP requests are made with headers including
"X-API-Key"and"Content-Type": "application/json". - SSL certificate validation is skipped (
skipSslCertificateValidation: true), which may require attention in secure environments.
Troubleshooting
Common issues:
- Invalid or missing Order ID will cause the API to return errors or empty results.
- Incorrect or expired API key will result in authentication failures.
- Network connectivity issues to the Livo API endpoint.
- If the API changes or the endpoint is unavailable, requests will fail.
Error messages:
- Errors thrown by the API are caught and can be output as error messages if "Continue On Fail" is enabled.
- Typical errors include "Order not found", "Unauthorized", or "Bad Request".
Resolutions:
- Verify the Order ID is correct and exists in the system.
- Ensure the API key credential is valid and has necessary permissions.
- Check network access and endpoint URL correctness.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- Livo API Documentation (Assumed placeholder, replace with actual if available)
- n8n HTTP Request Node documentation for understanding request options.
- General REST API best practices for troubleshooting authentication and request errors.