Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Customer → Create
AI-generatedOverview
This node integrates with the Haravan platform, allowing users to interact with various Haravan resources such as customers, orders, products, and accounts. Specifically, for the Customer - Create operation, it enables the creation of new customer records in a Haravan store. This is useful for automating customer management workflows, syncing customer data from other systems, or onboarding new customers programmatically.
Practical examples include:
- Automatically adding new customers collected from a web form into Haravan.
- Syncing customer data from a CRM system into Haravan.
- Creating test customers during development or QA processes.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings for the operation. |
| - Logging Request | Boolean flag to enable logging of each API request sent to Haravan for debugging purposes. |
The "Options" property currently supports one option:
- Logging Request: When enabled, the node logs detailed information about each API request made to Haravan, which helps in troubleshooting and debugging.
Output
The node outputs an array of JSON objects representing the results of the executed operations. For the Customer Create operation, each output item contains:
executionId: The unique identifier of the current workflow execution.resource: The resource type, e.g., "Customer".operation: The operation performed, e.g., "Create".status: The status of the operation, typically"completed"if successful.timestamp: ISO string timestamp when the operation was completed.
If multiple items are processed, the output will be an array of such result objects.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- The node depends on an external Haravan library (imported as
h), which likely handles API communication. - Proper configuration of the Haravan API credentials within n8n is necessary.
- No additional environment variables are explicitly required based on the provided code.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or missing API credentials.
- Network errors or timeouts when connecting to the Haravan API.
- Invalid input data causing the API to reject customer creation requests.
Error handling:
- If an error occurs during processing an item, and "Continue On Fail" is enabled, the node will add an error object alongside the input data for that item and continue processing subsequent items.
- Without "Continue On Fail", the node throws an error stopping execution, providing the item index where the failure occurred.
Debugging tips:
- Enable the "Logging Request" option to get detailed logs of API requests for troubleshooting.
- Check the workflow execution logs for error messages and stack traces.
- Verify that all required customer fields are correctly set before executing the node.
Links and References
- Haravan Official Website
- n8n Documentation on Custom Nodes
- Haravan API Documentation (for details on customer creation endpoints)