Actions8
- Stock Actions
- Autopart Actions
- Vehicle Actions
Overview
The node interacts with the Hubbi services API to manage stock data. Specifically, the "Delete Stock" operation allows users to remove a stock item identified by its Part ID from their inventory. This is useful for dealers or buyers who need to keep their stock records up-to-date by deleting parts that are no longer available or relevant.
Practical examples:
- A dealer removes a discontinued autopart from their stock list.
- A buyer deletes a part they no longer intend to purchase or track.
Properties
| Name | Meaning |
|---|---|
| User Type | Selects the type of user accessing the Hubbi services: either "Dealer" or "Buyer". This affects available operations and data access. |
| Part ID | The unique identifier of the part in stock to be deleted. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any error messages returned by the Hubbi API. There is no indication that binary data is output by this node.
Example output JSON might look like:
{
"success": true,
"message": "Stock item deleted successfully",
"deletedPartId": "12345"
}
Dependencies
- Requires an API key credential for authenticating with the Hubbi services.
- The base URL for API requests is configured via credentials.
- The node depends on the Hubbi REST API being accessible and properly configured for the authenticated user.
Troubleshooting
Common issues:
- Invalid or missing Part ID: The node requires a valid Part ID to delete; ensure this is provided.
- Authentication errors: Verify that the API key credential is correct and has sufficient permissions.
- Network or API downtime: Check connectivity and Hubbi service status if requests fail.
Error messages:
- "Part ID is required": Ensure the Part ID property is set.
- "Unauthorized": Check API key validity and permissions.
- "Not Found": The specified Part ID does not exist in the user's stock.
Resolving these typically involves verifying input parameters, credentials, and network connectivity.