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 a list of repair tickets. Specifically, the "Get Repairs" operation fetches paginated repair warranty tickets with optional filtering by keyword, status, and date range. This is useful for businesses managing device repairs or warranty services who want to automate retrieval and processing of repair ticket data within their workflows.

Practical examples:

  • Automatically fetching recent repair tickets daily to update an internal dashboard.
  • Filtering repair tickets by status (e.g., pending, completed) to trigger follow-up actions.
  • Searching repair tickets by keywords related to device issues or customer notes.

Properties

Name Meaning
Page Size Number of repair tickets to return per page (pagination size).
Current Page Current page number to retrieve in the paginated results.
Keyword Search keyword to filter repair tickets by matching text fields.
Status Filter repair tickets by their status (e.g., open, closed).
Start Date Start date to filter repair tickets created or updated after this date/time.
End Date End date to filter repair tickets created or updated before this date/time.

Output

The output is a JSON array where each item corresponds to a repair ticket retrieved from the Livo API endpoint /api/ecommerce/repairwarrantyticket. Each JSON object contains the full details of a repair ticket as returned by the API, including metadata such as ticket ID, status, customer info, device details, and timestamps.

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 the credentials.
  • HTTP requests are made with headers including X-API-Key and Content-Type: application/json.
  • SSL certificate validation is skipped (skipSslCertificateValidation: true), which may require attention in secure environments.

Troubleshooting

  • Common issues:
    • Invalid or missing API key will cause authentication failures.
    • Incorrect date formats for start/end dates may result in no data or errors.
    • Requesting pages beyond available data returns empty results.
  • Error messages:
    • Errors thrown by the HTTP request helper typically include the API error message.
    • If the node is set to continue on fail, errors are returned in the output JSON under an error field.
  • Resolutions:
    • Verify API key validity and permissions.
    • Ensure date inputs are correctly formatted ISO strings.
    • Adjust pagination parameters to valid ranges.

Links and References

Discussion