Zen ERPInstall

Summary

Ground claims in the properties and the source. Prefer the source when they disagree about runtime behaviour (inputs consumed, side effects, return shape). Be specific about inputs (which parameters matter, which are optional) and the resulting effect or returned data. Don't invent behavior. If neither properties nor source make a detail clear, describe what's declared, not what you guess. Avoid filler (

Inputs

• shipping_shipmentOpFinish_path — Collection of path parameters for the ShipmentOpFinish operation under the Shipping resource.

Output shape

Returns an array of n8n items, each containing a json field with the handler's result and a pairedItem reference. If the handler returns undefined, no item is pushed for that input.

The node processes items sequentially; errors are either thrown or returned as JSON with an error key depending on continueOnFail setting.

Examples

Example 1: A workflow author sets the `id` parameter (number, default 0) to specify which shipment to finish, connects the Zen ERP node with `zenApi` credentials, and sets the resource to `Shipping` and operation to `ShipmentOpFinish`. The node returns the shipment finish result as n8n item JSON.

In the node editor, the workflow author selects the Shipping resource and ShipmentOpFinish operation from the UI dropdown. The id field (number) becomes available as a path parameter. The node requires zenApi credentials. Input data flows through the node's main input, and the output provides the handler's result as structured JSON items.