Overview
This node interacts with the Wolt API to manage venue menus and related data. Specifically, for the "Update Menu Options" operation, it allows bulk updating of menu option values such as price and visibility for a given venue. This is useful for venues that want to efficiently update multiple menu options at once without manually changing each one individually.
Practical examples include:
- Adjusting prices or availability of add-ons or modifiers in a restaurant's menu.
- Enabling or disabling certain menu options based on time of day or stock levels.
- Quickly reflecting changes made in a POS or menu management system onto the Wolt platform.
Properties
| Name | Meaning |
|---|---|
| Venue ID | The unique identifier of the venue whose menu options you want to update. |
| Data | JSON object containing the menu options data to send to the API for updating. Typically includes an array of option values with their updated properties like price or visibility. |
Output
The node outputs an array of JSON objects representing the response from the Wolt API for each input item processed. For the "Update Menu Options" operation, the output JSON contains the API's confirmation or details about the updated menu options.
If an error occurs during the API call, the output JSON will contain an error field with the error message.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Wolt API.
- Needs username and password credentials for Basic Authentication.
- The node uses the Wolt POS Integration Service endpoint, which differs between production and development environments.
- Proper configuration of these credentials and environment selection is necessary for successful API communication.
Troubleshooting
Common issues:
- Invalid or missing credentials can cause authentication failures.
- Incorrect Venue ID may result in "not found" errors.
- Malformed JSON in the Data property can lead to request errors.
- Using the wrong environment URL (production vs development) might cause unexpected results.
Error messages:
- Errors returned from the API are passed through in the output JSON under the
errorfield if "Continue On Fail" is enabled. - NodeOperationError is thrown otherwise, indicating failure in the HTTP request or response handling.
- Errors returned from the API are passed through in the output JSON under the
Resolutions:
- Verify that the API key, username, and password are correct and have sufficient permissions.
- Double-check the Venue ID for accuracy.
- Validate the JSON structure in the Data property before running the node.
- Ensure the environment setting matches the intended target (production or development).
Links and References
- Wolt API Documentation
- Wolt POS Integration Service (Production)
- Wolt POS Integration Service Development (Development)