Actions21
- Orders Actions
- Products Actions
- Repairs Actions
- Customers Actions
Overview
This node interacts with the Livo API to retrieve customer data. Specifically, the "Get Customers" operation fetches a paginated list of customers from the system, allowing filtering and sorting based on various criteria such as keyword search, status, date range, and sort field.
This node is useful in scenarios where you want to integrate customer data retrieval into your workflows, for example:
- Synchronizing customer lists between Livo and another CRM or database.
- Automating reports or notifications based on customer activity or status.
- Filtering customers dynamically based on keywords or date ranges for targeted marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Page Size | Number of customer records to return per page (default 20). |
| Current Page | Current page number to retrieve (default 1). |
| Keyword | Search keyword to filter customers by name or other searchable fields. |
| Status | Filter customers by their status (e.g., active, inactive). |
| Start Date | Start date to filter customers created or updated after this date/time. |
| End Date | End date to filter customers created or updated before this date/time. |
| Sort By | Field name to sort the returned customers by (e.g., name, creation date). |
Output
The output is a JSON object representing the response from the Livo API endpoint /api/order/customer with query parameters corresponding to the input properties.
- The JSON structure contains an array or list of customer records matching the filters.
- Each customer record typically includes details such as customer ID, name, email, phone, address, status, 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.
- The 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 failures.
- Incorrect date formats for startDate or endDate may result in API errors or empty results.
- Requesting pages beyond available data will return empty arrays.
- Network connectivity issues can cause request timeouts or failures.
Error messages:
- Errors thrown by the API will be caught and can be output as error messages if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, invalid parameter errors, or server errors.
Resolution tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Ensure date/time inputs are valid ISO strings or compatible formats.
- Use reasonable page sizes and current page numbers within expected ranges.
- Check network access to the Livo API endpoint.
Links and References
- Livo API Documentation (Assumed, replace with actual link if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls.
- General best practices for pagination and filtering in REST APIs.