Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
This node integrates with the Hubbi services to retrieve and manipulate data related to automotive parts, stock, and vehicles. Specifically, for the Stock resource and the Get Autopart in Stock operation, it allows users (either dealers or buyers) to fetch detailed information about a specific autopart available in stock.
Typical use cases include:
- A dealer wanting to check the availability and details of a particular autopart in their inventory.
- A buyer querying the stock status of an autopart before making a purchase decision.
For example, a dealer can input the Part ID to retrieve current stock levels, pricing, and other relevant details for that autopart.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing the Hubbi services. Options: Dealer or Buyer. This affects data access and available operations. |
| Part ID | The unique identifier of the autopart to retrieve from stock. Required when performing get, update, or delete operations on parts. |
Output
The node outputs JSON data representing the autopart's stock information. This typically includes fields such as part identifiers, stock quantities, pricing, descriptions, and possibly metadata related to the autopart.
If binary data is returned (not indicated explicitly here), it would represent associated files or images related to the autopart.
Dependencies
- Requires an API key credential for authenticating with the Hubbi services.
- The base URL for the API is configurable via credentials.
- The node depends on the Hubbi REST API endpoints to fetch stock and autopart data.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly configured in the node credentials.
- Invalid Part ID: If the Part ID does not exist or is malformed, the API may return an error or empty result. Verify the Part ID before running the node.
- User Type mismatch: Selecting a User Type that does not have permission for the requested operation may cause authorization errors.
- Network issues: Connectivity problems to the Hubbi API endpoint will cause request failures; verify network access and API availability.