NetSuite REST icon

NetSuite REST

Call NetSuite SuiteTalk REST operations.

Actions979

Inbound Shipment → Insert or update record

AI-generated

Summary

Create or replace an inbound shipment record identified by an external ID.

Inputs

  • Debug Mode — Include full request and response details in the output.
  • Id (required) — External identifier of the inbound shipment to insert or update; used as the path parameter in the NetSuite REST API.
  • Additional Fields — Object containing any inbound shipment fields to set or update. Optional fields include dates (actualDeliveryDate, actualShippingDate, expectedDeliveryDate, expectedShippingDate), billOfLading, externalDocumentNumber, shipmentMemo, shipmentNumber, shipmentStatus, vesselNumber, and nested collections such as items, customForm, prefer, replace, replaceSelectedFields, and custom fields extensions.
  • Custom Fields — An array of custom field entries, each specifying a field name (selected via loadCustomFields) and a value of the chosen data type.

Output shape

a single record representing the created or updated inbound shipment (JSON). If Debug Mode is true, the output also includes the raw HTTP request and response for each operation.

The server may return HTTP 201 on creation or 200 on update; the output payload is the resource representation returned by NetSuite. Fields omitted in the request are left unchanged on update.

Examples

Example 1: Create a new inbound shipment with minimal fields

Set Id to "SHIP001", leave other fields empty, optional debug mode off. The workflow returns the new inbound shipment record.

Example 2: Update shipment status and dates

Set Id to "SHIP001", set Additional Fields.shipmentStatus to "inTransit" and Additional Fields.actualDeliveryDate to a concrete date. The node sends a PUT and returns the updated record.

Example 3: Debug request and response

Enable Debug Mode, set any fields, and observe the output containing both the request JSON sent to NetSuite and the full response.

Discussion