Livo icon

Livo

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

Actions21

Overview

The "Update Order" operation in this node allows users to modify existing order records via the Livo API. This operation is useful for updating details such as the order type, customer, branch, notes, tags, responsible user, and the list of products included in the order. It is beneficial in scenarios where order information changes after creation, such as correcting customer details, adding or removing products, or updating internal notes.

Practical examples include:

  • Changing the assigned branch or user responsible for an order.
  • Adding tags to categorize or prioritize orders.
  • Updating the list of products if the customer modifies their purchase.

Properties

Name Meaning
Order ID The unique identifier of the order to update (required).
Order Type Numeric type of the order; typically 1 for standard orders (required).
Customer ID Numeric ID representing the customer associated with the order (required).
Branch ID Numeric ID of the branch handling the order (required).
Note Additional notes or comments about the order (optional, defaults to "N/A").
Tags A list of tags (strings) to label or categorize the order (optional).
User Responsible ID Identifier of the user responsible for managing the order (required).
Order Details Collection of products included in the order; each product requires a Product ID (required).

Output

The output JSON contains the response from the Livo API after attempting to update the order. This typically includes the updated order data or confirmation of the update operation. If the update fails and the node is configured to continue on failure, the output will contain an error message describing the issue.

No binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Livo API.
  • The node expects the environment URL and API key to be provided through credentials.
  • HTTP requests are made with JSON payloads and require proper network connectivity to the Livo API endpoint.

Troubleshooting

  • Common issues:
    • Invalid or missing Order ID will cause the update to fail.
    • Incorrect or missing required fields like Customer ID, Branch ID, or User Responsible ID can result in errors.
    • Network or authentication failures due to invalid API keys or endpoint misconfiguration.
  • Error messages:
    • Errors returned by the API will be passed through in the output JSON under an error field if "Continue On Fail" is enabled.
    • Typical errors might include "Order not found", "Invalid input data", or "Unauthorized".
  • Resolution:
    • Verify that all required fields are correctly filled.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity and API endpoint configuration.

Links and References

Discussion