Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The node integrates with the Hubbi services to retrieve data related to stock, autoparts, and vehicles. Specifically, for the Stock resource with the List Stock operation, it fetches a list of stock items available to the user. This is useful for dealers or buyers who want to programmatically access inventory information from Hubbi.
Common scenarios include:
- Dealers listing their current stock to synchronize with other systems.
- Buyers browsing available stock items to find parts or vehicles.
- Automating inventory updates or monitoring stock levels.
Example: A dealer could use this node to pull all stock items daily and update their internal database or website listings automatically.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing Hubbi services. Options: "Dealer" or "Buyer". Determines accessible resources and operations. |
Output
The node outputs JSON data representing the list of stock items retrieved from Hubbi. Each item in the output typically contains details about individual stock entries such as part identifiers, quantities, descriptions, and other relevant metadata.
If binary data is returned (not indicated explicitly here), it would represent associated files or documents related to stock items, but this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating with Hubbi services.
- The base URL for API requests is configured via credentials.
- Network access to Hubbi's API endpoints is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Empty results: Verify that the selected User Type matches the actual account type and that there is stock data available.
- Network issues: Confirm connectivity to the Hubbi API endpoint and check for any firewall restrictions.
- Invalid property values: Make sure the "User Type" property is set correctly; invalid combinations may cause the node to fail or return no data.