Overview
This node integrates with the Wolt API to update menu items for a specified venue. It is designed to bulk update item data such as price and visibility, allowing venues to synchronize their menus efficiently between their point-of-sale (POS) or menu management systems and the Wolt app. This saves time and effort by automating updates rather than manually changing each item on the Wolt platform.
Common scenarios include:
- Updating prices of multiple menu items after a price change.
- Changing the visibility status of items (e.g., hiding unavailable dishes).
- Bulk editing item details in response to menu changes.
Practical example: A restaurant updates its menu prices in their POS system; this node can be used to push those changes automatically to Wolt, ensuring customers see the latest prices without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Venue ID | The unique identifier of the venue whose menu items are to be updated. |
| Data | JSON object containing the data to send to the API for updating items. Typically includes an array of item updates specifying fields like price, visibility, etc. |
Output
The node outputs an array of JSON objects corresponding to the API responses for each input item processed. Each JSON object contains the response from the Wolt API after attempting to update the menu items.
If the operation fails for any input and "Continue On Fail" is enabled, the output will include an error object with the error message for that particular input.
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 supports two environments: production and development, which affect the base URL used for API requests.
- Proper configuration of these credentials and environment selection is necessary for successful API communication.
Troubleshooting
- Authentication errors: If the API key, username, or password are incorrect or missing, the node will fail to authenticate. Verify credentials and ensure they are correctly configured.
- Invalid Venue ID: Providing an incorrect or non-existent venue ID will cause the API to return an error. Confirm the venue ID is valid.
- Malformed Data JSON: The
Dataproperty must be a valid JSON object matching the expected structure by the Wolt API. Invalid JSON or incorrect fields may cause request failures. - Network issues: Connectivity problems or incorrect environment settings (production vs development) can lead to failed requests.
- Error messages: The node throws errors with messages returned from the API or network layer. Enabling "Continue On Fail" allows processing to continue while capturing errors per item.
Links and References
- Wolt API Documentation (for detailed API specs and data formats)
- n8n HTTP Request Node documentation (for understanding how HTTP requests are made within n8n)
If you need further details on other operations or resources, feel free to ask!