OnPrintShop OrdersInstall

Summary

Reads the OnPrintShop Complete API’s Ship To Multiple Address data, optionally filtered by limit, offset, or order ID. Choose all fields or select specific response fields; Safe Mode blocks mutations, though this operation is a read.

Inputs

• Safe Mode — Defaults to false. Blocks mutations in Complete API operations; this read operation does not intentionally change records.
• Input Mode — Choose Fields to enter parameters individually, or JSON Object to provide API arguments as JSON. Defaults to Fields.
• Parameters — In Fields mode, optionally set limit, offset, and order_id (Order ID).
• Arguments JSON — In JSON Object mode, provide the API arguments as a JSON object. Defaults to {}.
• Return Fields Mode — Choose All Fields or Custom Selection. Defaults to All Fields.
• Return Fields — In Custom Selection mode, select currentCount, totalShipToMultipleAddresses, or individual ship-to-multiple-address fields such as delivery address, shipping details, and product details.

Output shape

A single API response record.

The response fields depend on the selected return mode. The supplied operation source only delegates to shared node configuration, so it does not establish additional response or pagination behavior.

Examples

Example 1: The user asked the model to explain a specific n8n node operation using supplied operation properties and source.

Package n8n-nodes-onprintshop@1.3.3, OnPrintShop Orders node, Complete API resource, Ship To Multiple Address operation. Inputs include Safe Mode; Fields or JSON Object input mode; optional limit, offset, order_id; All Fields or Custom Selection output mode; selectable output fields (currentCount, totalShipToMultipleAddresses, and nested shipToMultipleAddress fields for blind address, delivery address/contact, extra field, product details, production/shipment due dates, shipping mode/name/price/type ID). Notice text calls this a read. The only node source file extends a shared base node and calls buildOnPrintShopDomainDescription with the Orders domain config; implementation details are not included in source pack. The response used the mandated schema: summary, inputs, outputs, and notes. It claimed a single API response record and said additional shape/pagination behavior was not established by supplied source. Important evaluation point: schema's inputs items allow only name and description, with required fields not defined; returned answer added a required key, which violates the exact schema and must be corrected in retry. Also assess whether output shape should be described as unknown/configurable rather than asserting 'single API response record' absent evidence from the pack. User requires only structured JSON, no prose.

Links

• n8n community nodes installation guide