Actions21
- Orders Actions
- Products Actions
- Repairs Actions
- Customers Actions
Overview
This node integrates with the Livo API to retrieve detailed information about customers. Specifically, the "Get Customer Detail" operation fetches comprehensive data for a single customer based on their unique ID. This is useful in scenarios where you need to access or verify specific customer information within workflows, such as CRM updates, order processing, or customer support automation.
Practical examples:
- Fetching a customer's profile details before creating an order.
- Retrieving customer information to personalize email campaigns.
- Accessing customer data to validate identity during support ticket creation.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer whose details are to be retrieved (required). |
| Page Size | Number of customer records to return per page (used for pagination; default is 20). |
| Current Page | The current page number for paginated results (default is 1). |
| Start Date | Filter to include only customer data from this start date onwards. |
| End Date | Filter to include only customer data up to this end date. |
Output
The output JSON contains the detailed information of the requested customer as returned by the Livo API. This typically includes fields such as customer name, contact details, address, and other relevant metadata associated with the customer record.
If multiple records are returned (in case of pagination), the output will contain an array of customer objects accordingly.
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 URL of the Livo API environment and the API key to be configured in the credentials.
- Network connectivity to the Livo API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Customer ID parameter will cause the API request to fail.
- Incorrect or expired API key will result in authentication errors.
- Network issues or incorrect API base URL configuration can lead to connection failures.
Error messages:
"error": "Invalid Customer ID": Verify that the Customer ID provided exists and is correctly formatted."error": "Unauthorized"or similar: Check that the API key credential is valid and has not expired.- Timeout or network errors: Ensure the Livo API endpoint is reachable from your environment.
To resolve errors, confirm all required parameters are set, credentials are correct, and the API service is operational.
Links and References
- Livo API Documentation (Assumed link, replace with actual if available)
- n8n documentation on Creating Custom Nodes