Livo icon

Livo

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

Actions21

Overview

The node interacts with the Livo API to manage customer data, specifically allowing you to update existing customer records. This operation is useful in scenarios where customer information such as name, email, phone number, or address needs to be modified or corrected after initial creation. For example, if a customer's contact details change or need to be standardized, this node can update those details in the system.

Properties

Name Meaning
Customer ID The unique identifier of the customer to update (required).
Customer Name The full name of the customer (required).
Email The customer's email address (optional).
Phone The customer's phone number (optional).
Address The customer's physical address (optional).

Output

The output JSON contains the response from the Livo API after attempting to update the customer record. Typically, this will include the updated customer data or confirmation of the update operation. If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Livo API.
  • The node expects the Livo API base URL to be provided via environment configuration.
  • The HTTP requests are made with headers including the API key and content type set to JSON.
  • SSL certificate validation is skipped (skipSslCertificateValidation: true), which may require attention depending on your environment's security policies.

Troubleshooting

  • Common issues:
    • Invalid or missing Customer ID will cause the update to fail.
    • Incorrect API key or expired credentials will result in authentication errors.
    • Network connectivity issues or incorrect API endpoint configuration can cause request failures.
  • Error messages:
    • Errors returned by the API will be included in the output if "Continue On Fail" is enabled.
    • Typical errors might include "Customer not found", "Invalid input data", or "Unauthorized".
  • Resolutions:
    • Verify that the Customer ID exists and is correct.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network access and API endpoint correctness.
    • Enable "Continue On Fail" to handle errors gracefully within workflows.

Links and References

  • Livo API Documentation (Replace with actual link if available)
  • n8n documentation on HTTP Request Node for understanding underlying HTTP calls.
  • General best practices for managing API credentials securely in n8n workflows.

Discussion