Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The node integrates with Hubbi services to retrieve detailed information about autoparts, specifically focusing on part specifications in this context. It is designed for users who need to access comprehensive data about automotive parts, such as dealers managing inventory or buyers seeking detailed part information before purchase.
Common scenarios include:
- Dealers verifying and managing part details within their stock.
- Buyers researching specific part numbers and brands to ensure compatibility or quality.
- Automotive service providers needing accurate part specifications for repairs or replacements.
For example, a dealer might use this node to fetch up-to-date specifications of a part by entering its part number and brand name, ensuring the correct item is stocked and described accurately in their system.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing the Hubbi services. Options: "Dealer" or "Buyer". This affects available operations and data access. |
| Part Number | The unique identifier of the autopart to search or query specifications for. Required when performing search, part specifications, or quotation operations. |
| Brand Name | The brand associated with the autopart. Required for retrieving part specifications or quotations. |
Output
The node outputs JSON data containing detailed specifications of the requested autopart. This includes attributes such as dimensions, compatibility, technical details, and other descriptive metadata relevant to the part.
If binary data output is supported (not explicitly shown in the provided code), it would typically represent files or images related to the part, such as datasheets or diagrams.
Dependencies
- Requires an API key credential for authenticating with the Hubbi services.
- Needs the base URL of the Hubbi API configured in the node credentials.
- Relies on the Hubbi REST API endpoints to fetch autopart data.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node's credentials.
- Incorrect part number or brand name: Verify that the input values match existing records in the Hubbi database; otherwise, the node may return empty results or errors.
- User Type mismatch: Selecting the wrong user type may limit available operations or data access, leading to unexpected results.
- Network issues: Connectivity problems can cause request failures; check network settings and API availability.
Common error messages might include authentication failures, resource not found, or validation errors on input parameters. Resolving these typically involves checking credentials, input correctness, and API status.