OrderlyInstall

Summary

Lists Orderly order headers using the OrderService.ListHeaders API. Provide an OrderQuery JSON object in Input JSON; by default, the node emits one n8n item for each element in the response data array.

Inputs

• Input JSON — OrderQuery request as JSON; defaults to the incoming item’s JSON. Unknown fields are ignored when converting the request.
• Split Data — Defaults to true. When the response contains a data array, emit each element as a separate n8n item. Disable to emit the full response as one item.

Output shape

A list of n8n items containing order header data.

With Split Data enabled, each response data element becomes an item; if data is not an array, the full response is emitted as one item. With splitting disabled, the full response is emitted as one item. Output items retain their pairing to the corresponding input item.

Examples

Example 1: Default split output

Input JSON defaults to the incoming item’s JSON, and Split Data is true by default. The response contains two order headers in its data array: {"data":[{"id":"ord-101","status":"open"},{"id":"ord-102","status":"booked"}]} . The output is two n8n items, one for each header: {"id":"ord-101","status":"open"} and {"id":"ord-102","status":"booked"}.

Example 2: Keep the full response

Set Split Data to false. For a response such as {"data":[{"id":"ord-101","status":"open"}],"nextPageToken":"abc"}, the node emits one item containing the full response, including data and nextPageToken.

Links

• n8n community nodes installation guide