Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The node provides integration with Hubbi services, specifically enabling users to search for autoparts. It supports two user types: Dealer and Buyer, which influence the available operations and data access.
The Search Autopart operation allows users to find parts by various criteria such as part name, part number, barcode, vehicle details, position on the vehicle, stock availability, and geographic location (UF). This operation is useful in scenarios like:
- Dealers looking up parts in their inventory or catalog.
- Buyers searching for specific autoparts compatible with their vehicles.
- Advanced searches filtering parts by detailed attributes and stock presence.
Practical examples include:
- A dealer searching for all front-positioned parts currently in stock in a specific state.
- A buyer searching for a part by its barcode or part number to verify availability.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing Hubbi services. Options: Dealer, Buyer. Determines accessible resources and operations. |
| Part Name | The name of the autopart to search for. Used in basic search queries. |
| Part Number | The unique identifier or code of the autopart. Can be used in multiple operations including search, specifications lookup, and quotations. |
| Advanced Search | Enables additional search filters beyond basic part name or number. When enabled, more fields become available for refined queries. |
| Barcode | The barcode associated with the autopart. Available only when advanced search is enabled. |
| Vehicle | Specifies the vehicle model or identifier to filter parts compatible with that vehicle. Available only when advanced search is enabled. |
| Position | Filters parts based on their position on the vehicle. Multiple selections allowed. Options: Front, Left, Lower, Rear, Right, Upper. Available only when advanced search is enabled. |
| Only in Stock | Limits results to parts currently in stock. Boolean toggle. Available only when advanced search is enabled. |
| UF | Filters parts by Brazilian states (Unidades Federativas) where the parts are stocked or available. Multiple selections allowed. Available only when advanced search and "Only in Stock" are enabled. |
Output
The node outputs JSON data representing the search results from the Hubbi service. The structure typically includes an array of autopart objects matching the search criteria, each containing details such as part identifiers, descriptions, compatibility information, stock status, and possibly pricing or quotation data depending on the operation.
If binary data were involved (not indicated here), it would represent files or images related to parts, but this operation focuses on JSON data output.
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 perform searches and retrieve autopart data.
Troubleshooting
- No results returned: Check if the search parameters are too restrictive, especially when using advanced search filters like position, stock availability, or UF. Try broadening the criteria.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Invalid parameter errors: Verify that the input values conform to expected formats, e.g., valid part numbers or vehicle identifiers.
- Network or timeout issues: Confirm network connectivity to the Hubbi API endpoint and consider increasing timeout settings if large datasets are queried.