Vendus icon

Vendus

Interact with Vendus API for invoicing and business management. Developed by Pixel Infinito (https://pixel.ao)

Product → Get Product Stock

AI-generated

Overview

The node interacts with the Vendus API to retrieve stock information for a specific product. It is designed to fetch the current stock levels of a product identified by its name or ID. This functionality is useful in inventory management scenarios where users need to monitor product availability, update stock records, or trigger workflows based on stock changes.

Practical examples include:

  • Automatically checking stock before creating an order.
  • Monitoring inventory levels to trigger restocking alerts.
  • Integrating stock data into dashboards or reports.

Properties

Name Meaning
Product Name or ID The identifier of the product whose stock you want to retrieve. Can be selected from a list or specified via an expression.
Options Additional settings for the operation:
- Enable Debug Logging: Enables detailed debug logs for troubleshooting API calls.

Output

The node outputs JSON data representing the stock information of the requested product as returned by the Vendus API. The exact structure depends on the API response but typically includes fields such as available quantity, reserved stock, and other relevant inventory details.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Vendus API.
  • The node expects the base URL of the Vendus API to be configured in the credentials.
  • Optional debug logging can be enabled to assist with troubleshooting API requests.

Troubleshooting

  • Missing or incorrect Product ID: If the product identifier is not provided or invalid, the node will throw an error indicating the required parameter is missing.
  • API authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
  • Network or API errors: Enabling debug logging can help identify issues with request URLs, methods, or responses.
  • No routing configuration found: This error indicates an internal misconfiguration; verify that the resource and operation names are correct.

Links and References

Discussion