Actions21
- Orders Actions
- Products Actions
- Repairs Actions
- Customers Actions
Overview
This node integrates with the Livo API to manage e-commerce products, specifically allowing users to create new products in their online store. The "Create Product" operation sends product details such as name, SKU, price, category, and description to the Livo platform to add a new product record.
Typical use cases include:
- Automating product catalog updates by creating new products from external data sources.
- Integrating product creation into workflows that handle inventory management or supplier feeds.
- Quickly adding new items to an e-commerce system without manual entry.
For example, a retailer could use this node to automatically add new products received from suppliers into their online store database.
Properties
| Name | Meaning |
|---|---|
| Product Name | The name of the product to be created (required). |
| SKU | Stock Keeping Unit code, a unique identifier for the product variant. |
| Price | The selling price of the product as a number. |
| Category | The category under which the product should be classified. |
| Description | A textual description providing details about the product. |
Output
The node outputs a JSON object representing the response from the Livo API after attempting to create the product. This typically includes details of the newly created product such as its ID, name, SKU, price, category, description, and any other metadata returned by the API.
No binary data output is involved in 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 the credentials.
- The HTTP request uses JSON content type and includes the API key in headers.
- SSL certificate validation is skipped (
skipSslCertificateValidation: true), which may require attention depending on your environment.
Troubleshooting
- Common issues:
- Missing required fields like "Product Name" will likely cause the API to reject the request.
- Invalid API key or missing credentials will result in authentication errors.
- Network connectivity problems or incorrect environment URLs can cause request failures.
- Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Typical error messages might include validation errors for missing or invalid fields, unauthorized access due to bad API keys, or server errors.
- Resolution tips:
- Ensure all required properties are provided and valid.
- Verify API key and environment URL configuration.
- Check network access to the Livo API endpoint.
- Enable detailed logging to capture request and response details for debugging.
Links and References
- Livo API Documentation (Assumed placeholder, replace with actual URL if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls.
- General guidance on API Authentication for managing API keys securely.