Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The node integrates with the Hubbi services to manage stock and autoparts data. Specifically, for the "Stock" resource and the "Create Autopart in Stock" operation, it allows users (typically dealers) to add new autoparts into their stock inventory within the Hubbi system. This is useful for automotive parts dealers who want to programmatically update their stock records, ensuring accurate inventory management and pricing.
Practical examples include:
- Automatically adding newly acquired autoparts to stock after purchase.
- Syncing stock data from an external ERP or inventory system into Hubbi.
- Managing pricing and availability of parts dynamically based on sales or supply changes.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing Hubbi services: either "Dealer" or "Buyer". This affects available operations and data access. |
| Part Name | The name of the autopart to create in stock. |
| Part Code | A unique code identifier for the autopart. |
| Price | The price of the autopart. |
| Stock | The quantity of the autopart available in stock. |
| ERP ID | An optional identifier linking the autopart to an external ERP system. |
Note: The properties "Part Name", "Part Code", "Price", "Stock", and "ERP ID" are shown only when the operation is "createPart" or "updatePart".
Output
The node outputs JSON data representing the created autopart record in the stock system. This typically includes details such as the part's name, code, price, stock quantity, and any identifiers assigned by Hubbi.
If the node supports binary data output (not evident from the provided code), it would represent associated files or images related to the autopart, but no such indication is present here.
Dependencies
- Requires an API key credential for authenticating with the Hubbi services.
- Needs the base URL of the Hubbi API configured in credentials.
- Relies on the Hubbi REST API endpoints for stock and autopart management.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Validation errors if required fields like Part Name or Part Code are missing or malformed.
- Network connectivity problems preventing access to the Hubbi API.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and valid.
- "Validation error": Ensure all required input properties are provided and correctly formatted.
- "Network error" or "Timeout": Verify network connectivity and API endpoint availability.