Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Customer → Get All
AI-generatedOverview
This node integrates with the Haravan platform, enabling users to interact with various Haravan resources such as orders, products, and customers. Specifically, for the Customer - Get All operation, it retrieves a list of all customers from the Haravan system. This is useful in scenarios where you want to synchronize customer data, perform bulk analysis, or trigger workflows based on customer information.
Practical examples include:
- Exporting all customers to a CRM or marketing tool.
- Triggering follow-up emails or campaigns based on customer data.
- Synchronizing customer lists between Haravan and other platforms.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings: |
| - Logging Request | Boolean flag to enable logging of each API request sent to Haravan for debugging purposes. |
Output
The node outputs an array of JSON objects representing the results of the executed operation. For the "Get All" customer operation, the output JSON will contain customer data retrieved from Haravan.
The structure of each JSON object includes metadata about the execution such as:
executionId: Unique identifier for the current execution.resource: The resource type, e.g., "Customer".operation: The operation performed, e.g., "Get All".status: Status of the operation (e.g., "completed").timestamp: ISO string timestamp of when the operation was completed.
The actual customer data fields are expected to be included in the response body but are not explicitly detailed in the provided code snippet.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- Depends on the external Haravan library (
../../nqdev-libraries/haravan) for API interaction. - Needs proper configuration of credentials within n8n to connect to Haravan.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing access to Haravan API.
- Rate limiting or API quota exceeded errors from Haravan.
Error messages:
- Errors thrown during execution are wrapped and reported with item index context.
- If "continue on fail" is enabled, failed items are returned with error details instead of stopping the workflow.
Resolution tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Enable logging via the "Logging Request" option to debug API requests and responses.
- Check network connectivity and firewall settings.
- Review Haravan API limits and adjust usage accordingly.