Livo icon

Livo

Interact with Livo API for orders, products, customers, and repairs
Join our community

Actions21

Overview

This node integrates with the Livo API to manage orders, specifically allowing you to create new orders in the system. It is useful for automating order creation workflows, such as when receiving orders from an external source or integrating with other systems like e-commerce platforms or CRM tools.

For the Create Order operation under the Orders resource, the node sends a POST request to the Livo API with detailed order information including customer, branch, products, and additional metadata like tags and notes.

Practical examples:

  • Automatically creating an order when a customer places a purchase on your website.
  • Syncing orders from another sales platform into Livo for centralized management.
  • Creating orders programmatically based on inventory or sales triggers.

Properties

Name Meaning
Order Type Type of the order. Default is 1 (standard order).
Customer ID Numeric ID representing the customer placing the order.
Branch ID Numeric ID of the branch where the order is placed or processed.
Note Additional notes or comments about the order.
Tags Optional list of tags associated with the order. Each tag is a string value.
User Responsible ID ID of the user responsible for managing or processing the order.
Order Details List of products included in the order. Each product requires a Product ID (numeric).

Output

The node outputs the JSON response returned by the Livo API after creating the order. This typically includes details of the newly created order such as its unique identifier, status, timestamps, and any other metadata provided by the API.

If the API supports it, the output may also include error messages or validation feedback if the order creation fails.

The node does not output binary data 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 the credentials.
  • The HTTP requests are made with JSON content type and include the API key in headers.
  • SSL certificate validation is skipped (skipSslCertificateValidation: true), which might be relevant depending on your environment.

Troubleshooting

  • Common issues:

    • Missing or invalid API key will cause authentication failures.
    • Providing invalid or missing required fields (e.g., Customer ID, Branch ID) will result in API errors.
    • Incorrect product IDs in the order details may cause the API to reject the order.
    • Network connectivity issues or incorrect environment URL configuration can prevent successful API calls.

  • Error messages:

    • Errors returned by the API will be included in the node's output if "Continue On Fail" is enabled.
    • Typical error messages relate to validation failures, unauthorized access, or resource not found.

  • Resolution tips:

    • Verify that all required properties are correctly set and valid.
    • Ensure the API key credential is properly configured and has necessary permissions.
    • Check network connectivity and endpoint URLs.
    • Use the node’s debug logs to inspect outgoing requests and responses.

Links and References

Discussion