Wolt ClientAPI icon

Wolt ClientAPI

Interact with the Wolt API

Overview

This node integrates with the Wolt API to manage restaurant menus and related data for venues. Specifically, the "Create a Menu" operation allows users to create or replace the menu of a specified venue by sending structured menu data to Wolt's platform.

Common scenarios where this node is beneficial include:

  • Restaurants or food venues wanting to programmatically upload or update their entire menu on Wolt.
  • Automating menu synchronization between a point-of-sale (POS) system and Wolt.
  • Quickly replacing an existing menu with a new one without manual intervention.

For example, a restaurant could use this node to push a newly designed menu JSON to Wolt whenever they update their offerings, ensuring customers always see the latest items.

Properties

Name Meaning
Venue ID The unique identifier of the venue whose menu you want to create or replace.
Data The JSON-formatted menu data to send to the Wolt API. This should contain the full menu structure as expected by Wolt.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Wolt API after attempting to create or replace the menu. This typically includes confirmation details or error messages returned by the API.

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 HTTP requests to communicate with Wolt's POS integration service endpoints.
  • The environment (production or development) affects the base URL used for API calls.

Troubleshooting

  • Authentication errors: If the API key, username, or password are incorrect or missing, the node will fail with authorization errors. Verify credentials are correctly configured.
  • Invalid JSON in Data property: The "Data" field must be valid JSON matching Wolt's expected menu schema. Malformed JSON or incorrect structure will cause API errors.
  • Venue ID issues: Providing an invalid or non-existent venue ID will result in API errors indicating the venue was not found.
  • API endpoint errors: Network issues or incorrect environment settings can cause failures connecting to Wolt's API. Ensure the environment setting matches your intended target (production vs development).
  • Error handling: If "Continue On Fail" is enabled, the node will return error details in the output JSON instead of stopping execution.

Links and References

  • Wolt API Documentation (for detailed menu data format and API usage)
  • n8n HTTP Request Node documentation (for understanding how HTTP requests are made within n8n)

Discussion