Livo icon

Livo

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

Actions21

Overview

This node interacts with the Livo API to retrieve order data. Specifically, the "Get Orders" operation fetches a paginated list of orders from the system, allowing filtering and sorting based on various criteria such as keyword, status, date range, and sort field. This is useful for workflows that need to process or analyze order data, generate reports, or synchronize order information with other systems.

Practical examples:

  • Automatically retrieving recent orders every day to update an external CRM or ERP.
  • Filtering orders by status (e.g., only completed or pending) to trigger follow-up actions.
  • Searching orders by keywords or date ranges to generate custom sales reports.

Properties

Name Meaning
Page Size Number of transactions (orders) to return per page.
Current Page The current page number to retrieve in pagination.
Keyword Search keyword to filter orders by matching text fields.
Status Filter orders by their transaction status (e.g., pending, completed).
Start Date Start date to filter orders created on or after this date/time.
End Date End date to filter orders created on or before this date/time.
Sort By Field name to sort the returned orders by (e.g., date, status).

Output

The output is a JSON object representing the response from the Livo API's order endpoint. It contains the list of orders matching the specified filters and pagination parameters. The exact structure depends on the API but typically includes order details such as order ID, customer info, status, dates, and items.

No binary data output is produced by 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 the 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 errors.
    • Incorrect date formats or invalid filter values may result in empty responses or API errors.
    • Pagination parameters out of range might return no results.
  • Error messages:
    • Errors thrown by the API (e.g., 401 Unauthorized, 400 Bad Request) will be surfaced as error messages.
    • If "Continue On Fail" is enabled, errors will be returned as JSON objects with an error property containing the message.
  • Resolution tips:
    • Verify API key validity and permissions.
    • Ensure date/time inputs are correctly formatted ISO strings.
    • Adjust pagination parameters to valid ranges.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion