DukanInstall

Summary

Update the details of an existing stop desk in the Dukan system by providing its MongoDB ObjectId and the new data fields.

Inputs

• Stop Desk ID (required) — The MongoDB ObjectId of the stop desk to update.
• Use JSON — Boolean flag to specify if update data is provided as a raw JSON object.
• JSON — Raw JSON string containing update data when 'Use JSON' is enabled; all fields are optional according to UpdateStoreLocationStopDeskDto schema.
• Stop Desk Address — Optional updated address of the stop desk (use only if not using JSON input).
• Stop Desk Shipping Price — Optional updated shipping price for the stop desk; must be zero or positive (use only if not using JSON input).
• Allow Stop Desk Shipping Fake Price — Optional flag indicating if fake price for stop desk shipping is allowed (use only if not using JSON input).
• Stop Desk ID (custom) — Optional custom ID to assign to the stop desk (use only if not using JSON input).
• Stop Desk Shipping Fake Price — Optional fake shipping price for the stop desk; must be zero or positive (use only if not using JSON input).
• Allow Default Shipping Account — Optional flag to allow default shipping account usage (use only if not using JSON input).
• Default Shipping Account — Optional MongoDB ObjectId of the default shipping account (use only if not using JSON input and if 'Allow Default Shipping Account' is true).
• Is Active — Optional flag indicating if the stop desk is active (use only if not using JSON input).
• Force Custom Auth Header — Whether to override the configured Dukan API credentials with a custom API key for this request.
• Custom API Key — The custom API key to use when 'Force Custom Auth Header' is enabled.
• Force Custom Base URL — Whether to override the base URL from credentials with a custom base URL for this request.
• Custom Base URL — The custom base URL to use for API requests when 'Force Custom Base URL' is enabled (omit the '/v1/external' suffix).

Output shape

a single JSON object representing the updated stop desk data returned by the Dukan API

The node sends an update request to the Dukan API and returns the API response. Fields in the update payload are optional and depend on whether JSON input or individual fields are used. Authentication and base URL can be overridden per request with the force custom options.

Examples

Example 1: Update a stop desk's address and activate it without JSON input

Set 'Stop Desk ID' to the target ID, set 'Use JSON' to false, enter the new 'Stop Desk Address', set 'Is Active' to true, and leave other optional fields empty or default.

Example 2: Update a stop desk using a raw JSON object

Set 'Stop Desk ID' to the target ID, set 'Use JSON' to true, and provide the JSON string with the fields to update in the 'JSON' property.

Links

• n8n community nodes installation guide