Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Products → Get Product
AI-generatedOverview
This node integrates with the Haravan platform, specifically allowing users to interact with various resources such as products. The "Get Product" operation fetches product data from Haravan. This is useful for workflows that need to retrieve product details dynamically, for example, syncing product information into a CRM, updating inventory systems, or triggering actions based on product attributes.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of additional settings: |
| - Logging Request | Boolean option 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 operations. For the "Get Product" operation, the output JSON will contain product data retrieved from Haravan. Each item in the output corresponds to one execution result and includes fields such as:
executionId: Unique identifier for the execution.resource: The resource type, e.g., "Products".operation: The operation performed, e.g., "Get Product".status: Status of the operation, typically "completed".timestamp: ISO string timestamp when the operation was completed.
If the node encounters errors and is configured to continue on failure, error details are included alongside the input data for the failed item.
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 the external Haravan API service.
- No additional environment variables or configurations are explicitly required beyond the API credential.
Troubleshooting
- Common issues:
- API authentication failures due to invalid or missing credentials.
- Network connectivity problems preventing access to Haravan API.
- Rate limiting or quota exceeded errors from the Haravan API.
- Error messages:
- Errors thrown during execution include context about the item index causing the failure.
- If "Continue On Fail" is disabled, the node stops execution on the first error.
- Enabling the "Logging Request" option can help debug API request/response issues by providing detailed logs.
Links and References
- Haravan Official API Documentation
- n8n documentation on Creating Custom Nodes