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 repair tickets. Specifically, the "Create Repair" operation allows users to create a new repair ticket for devices that require servicing. This is useful in scenarios such as electronics repair shops or service centers where tracking repair requests, device details, and associated services is essential.

Practical examples include:

  • Creating a repair ticket when a customer brings in a smartphone for screen replacement.
  • Logging multiple devices under one repair order for bulk servicing.
  • Capturing detailed device information including accessories, device states (issues), and repair services requested.

Properties

Name Meaning
Ticket Type Type of repair ticket; currently, 1 represents a standard ticket.
Repair Type Type of repair: either "Single" device or "Multiple" devices.
Customer ID Numeric ID of the customer requesting the repair.
Branch ID Numeric ID of the branch handling the repair.
Device Name Name or model of the device being repaired.
Device Category ID Numeric category ID representing the type of device.
Serial Number Serial number of the device.
Lock Screen Key Identifier key for the lock screen security (e.g., password type).
Lock Screen Value The actual lock screen password, PIN, or pattern.
Repair Accessories JSON array of accessories related to the repair, e.g., [{"id": "39", "name": "Accessory name"}].
Device States JSON array describing device issues or states, e.g., [{"id": "69", "name": "Issue description"}].
Repair Services JSON array detailing repair services including pricing, employees involved, custom flags, and notes.

Output

The node outputs a JSON object representing the response from the Livo API after creating the repair ticket. This typically includes details of the newly created repair record such as its ID, status, and all submitted data fields.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with 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.

Troubleshooting

  • Invalid or missing API key: The API will reject requests without proper authentication. Ensure the API key credential is correctly set up.
  • Malformed JSON inputs: The properties repairAccessorys, repairDeviceStates, and repairServices expect valid JSON strings. Invalid JSON will cause errors.
  • Required fields missing: Fields like ticketType, repairCustomerId, brankId, and deviceCategoryId are required. Omitting them will likely result in API validation errors.
  • Incorrect branch or customer IDs: Using invalid numeric IDs may cause the API to fail or return errors indicating resource not found.
  • To resolve errors, verify input data correctness, ensure JSON formatting is valid, and confirm API credentials.

Links and References

Discussion