Overview
This node integrates with the Wolt API to manage venue menus and inventory. Specifically, the "Update Inventory" operation allows venues to bulk update inventory quantities for items listed on Wolt. This is useful for keeping stock levels accurate and preventing orders for out-of-stock items. For example, a restaurant can use this node to quickly update the available quantity of multiple menu items after a busy service or when new stock arrives.
Properties
| Name | Meaning |
|---|---|
| Venue ID | The unique identifier of the venue whose inventory you want to update. |
| Data | JSON object containing the inventory data to send to the API. Typically includes item IDs and their updated quantities. |
Output
The node outputs an array of JSON objects representing the response from the Wolt API for each input item processed. The structure depends on the API response but generally contains confirmation of the inventory update or error details if the request failed.
If the API returns binary data (not typical for this operation), it would represent raw response content, but this node primarily handles JSON responses.
Dependencies
- Requires an API key credential for authenticating with the Wolt API.
- Needs username and password credentials for Basic Authentication.
- The node dynamically selects the API base URL depending on whether the environment is set to production or development.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Common issues:
- Invalid or missing Venue ID will cause the API call to fail.
- Incorrectly formatted JSON in the Data property may result in API errors.
- Authentication failures due to invalid API key, username, or password.
- Network connectivity issues to the Wolt API endpoints.
Error messages:
- Errors returned by the Wolt API are passed through; these might include authorization errors or validation errors on the data sent.
- If the node is configured to continue on failure, errors are included in the output JSON under an
errorfield. - To resolve errors, verify credentials, ensure the Venue ID exists, and confirm the data format matches API expectations.
Links and References
- Wolt API Documentation (general reference for API endpoints and data formats)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.