Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The "Update Stock" operation in the Hubbi node allows users to modify existing stock information for autoparts within the Hubbi services platform. This operation is particularly useful for dealers who need to keep their inventory data current, such as updating quantities, prices, or part details after receiving new shipments or making sales.
Practical examples include:
- A dealer updating the stock count of a specific part after a sale.
- Adjusting the price of a part based on market changes.
- Correcting or adding ERP identifiers to synchronize with external systems.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing the service: either "Dealer" or "Buyer". Determines available operations and data access. |
| Part ID | The unique identifier of the part to update. This is required to specify which stock item to modify. |
| Part Name | The name of the part. Used to update or set the part's descriptive name. |
| Part Code | The code associated with the part, often used for internal tracking or cataloging. |
| Price | The price of the part. Allows updating the cost or sale price. |
| Stock | The quantity of the part currently in stock. Used to update inventory levels. |
| ERP ID | An external ERP system identifier for the part, enabling integration with enterprise resource planning software. |
Output
The node outputs JSON data representing the updated stock record. This typically includes the part's updated fields such as ID, name, code, price, stock quantity, and ERP ID. The output reflects the state of the stock item after the update operation has been applied.
If binary data were involved (e.g., images or documents), it would be included in a separate binary property, but this operation focuses on JSON data updates only.
Dependencies
- Requires an API key credential for authenticating with the Hubbi services API.
- The base URL for API requests is configured via credentials.
- Network connectivity to the Hubbi API endpoint is necessary.
Troubleshooting
- Missing Required Fields: If the Part ID is not provided, the node will fail because it cannot identify which stock item to update.
- Authentication Errors: Invalid or missing API credentials will result in authorization failures.
- Invalid Data Types: Providing non-numeric values for price or stock may cause errors.
- API Endpoint Issues: Network problems or incorrect base URL configuration can prevent successful communication with the Hubbi API.
To resolve these issues:
- Ensure all required properties are correctly filled.
- Verify that the API key credential is valid and has appropriate permissions.
- Confirm that numeric fields contain valid numbers.
- Check network connectivity and API URL settings.