Linker CloudInstall

Summary

Create a Linker Cloud order by sending the supplied dates, delivery email, COD and shipment prices, discount, payment transaction ID, items, and optional additional fields to the orders API. Choose UI mode to add items individually or JSON mode to provide an item array; the node returns the API response as one output item per input item.

Inputs

• Order Date, Execution Date, Execution Due Date (required) — Dates in YYYY-MM-DD HH:mm:ss format.
• Delivery Email (required) — Email address for delivery notifications.
• COD Amount, Shipment Price, Shipment Price Net, Discount (required) — Numeric order amounts; defaults are 0. COD Amount can be 0 when there is no cash on delivery.
• Payment Transaction ID (required) — Transaction ID, or an empty string if none.
• Items Input Mode — Choose UI (the default) to enter items individually, or JSON to provide a raw or expression-based JSON array. Each item needs an SKU and quantity; supported fields include description, EAN, gross and net unit prices, tax rate, and weight. In JSON mode, serial_numbers, custom_properties, source_data, and batch_numbers default to empty arrays when omitted.
• Additional Fields — Optional order number, billing and delivery details, carrier and payment metadata, comments, currency, tags, custom properties, validation errors, delivery configuration, and other order fields. Tags, custom properties, validation errors, and delivery configuration are parsed from JSON strings.

Output shape

A single record per input item containing the Linker Cloud API response for the created order.

The operation sends a POST request to /public-api/v1/orders. Invalid item JSON or malformed JSON in parsed additional fields causes an error; with Continue On Fail enabled, the output item contains an error message.

Links

• n8n community nodes installation guide