LivoInstall

Overview

This node integrates with the Livo API to manage various e-commerce related resources, including orders, products, repairs, and customers. Specifically, for the Products resource with the Get Products operation, it fetches a paginated list of products from the Livo e-commerce platform. This is useful for workflows that need to retrieve product data for inventory management, synchronization with other systems, or display purposes.

Typical use cases include:

• Retrieving a list of products to update an external database or CRM.
• Filtering products by keyword to find specific items.
• Implementing pagination or "load more" functionality in automation workflows.

Properties

Output

The node outputs an array of JSON objects representing the products retrieved from the Livo API. Each item corresponds to a product record as returned by the API endpoint /api/ecommerce/product. The exact structure depends on the API response but typically includes product details such as ID, name, SKU, price, category, and description.

No binary data output is produced by this operation.

Example output snippet (conceptual):

[
  {
    "id": 123,
    "name": "Product A",
    "sku": "SKU123",
    "price": 99.99,
    "category": "Category X",
    "description": "Description of Product A"
  },
  {
    "id": 124,
    "name": "Product B",
    "sku": "SKU124",
    "price": 149.99,
    "category": "Category Y",
    "description": "Description of Product B"
  }
]

Dependencies

• Requires an API key credential for authenticating requests to the Livo API.
• The node expects the base URL of the Livo environment and the API key to be provided via credentials.
• The HTTP requests are made with headers including "X-API-Key" and "Content-Type": "application/json".
• SSL certificate validation is skipped (skipSslCertificateValidation: true), which may be relevant depending on your environment.

Troubleshooting

• Common issues:
  • Invalid or missing API key will cause authentication failures.
  • Incorrect environment URL or network issues can lead to connection errors.
  • Pagination parameters out of range might result in empty responses.
• Error messages:
  • Errors thrown by the API (e.g., 401 Unauthorized) will be surfaced as error messages.
  • If continueOnFail is enabled, errors will be included in the output JSON under an error field instead of stopping execution.
• Resolution tips:
  • Verify API key validity and permissions.
  • Check network connectivity and correct environment URL.
  • Adjust pagination parameters to valid ranges.

Links and References

• Livo API Documentation (Assumed, replace with actual if available)
• n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/