Extensiv

The Extensiv node interacts with the Extensiv 3PL Warehouse Manager API (formerly 3PL Central / SecureWMS). It lets a workflow retrieve order and item details and update an order's routing, references, and attached documents in a warehouse management system — useful for syncing fulfillment data, enriching orders, and automating routing updates from logistics workflows.

Overview

The Extensiv node is essential when you need to:

• Retrieve order detail - Pull an order (and selected sub-collections) for processing or reconciliation
• Retrieve item detail - Pull a specific order item, with allocations and saved elements
• Update routing - Write carrier, tracking, BOL, and related routing fields back to an order
• Update references - Set saved-element name/value pairs (custom references) on an order
• Attach documents - Upload a file from workflow storage to an order

Configuration

Resource

The resource to operate on. Only Order is available.

Action

The operation to perform (default Get Item):

Action	Value	API call
Get Order	getOrder	GET /orders/{orderId}
Get Item (default)	getItem	GET /orders/{orderId}/items/{itemId}
Attach File	attachFile	POST /orders/{orderId}/documents
Update Routing	updateRouting	PUT /orders/{orderId}/routing
Update Reference	updateReference	PUT /orders/{orderId}/savedelements

Parameters

Which fields appear depends on the action:

Field	Shown for	Description
Order Id (required)	Get Order, Get Item, Attach File, Update Routing, Update Reference	The order identifier. Supports expressions.
Item Id (required)	Get Item	The order item identifier. Supports expressions.
Order Detail	Get Order	Sub-collections to include, as a multi-select: Order Items, Billing Details, Saved Elements, Packages, Contacts, Proposed Billing, Outbound Serial Numbers, Small Parcel, Parcel Options, All. Sent as the detail query parameter.
Item Detail	Get Order, Get Item	Item sub-collections to include: Saved Elements, Allocations, Allocations With Detail, All. Sent as the itemdetail query parameter.
File (required)	Attach File	A file reference from a previous node, uploaded to the order's documents. Supports expressions.
Reference Collection	Update Reference	One or more Name / Value pairs, written as the order's saved elements.
Routing fields	Update Routing	The routing values to set (see below). Only fields you provide are sent.

Update Routing fields

All optional; only the fields you set are included in the update: Is COD, Is Insurance, Requires Delivery Confirmation, Requires Return Receipt, SCAC Code, Carrier, Mode, Account, Load Number, Bill of Lading, Tracking Number, Trailer Number, Seal Number, Door Number, Pickup Date, Notes, Number of Units 1 (+ Type ID), Number of Units 2 (+ Type ID), Total Weight, Total Volume.

Credential

The Extensiv node requires an Extensiv credential (extensivAuth):

Field	Required	Description
Client ID	Yes	OAuth client ID.
Client Secret	Yes	OAuth client secret.
Login	Yes	The UserLoginName or UserID, sent as user_login_id during authentication.

The node authenticates with the OAuth client credentials grant: it requests a token from /AuthServer/api/token using the Client ID/Secret (HTTP Basic) plus the Login, then calls the API with Authorization: Bearer <token>. The API base URL defaults to https://secure-wms.com.

Output

The node returns the API response for the operation:

• Get Order / Get Item - The order or item record as JSON (including any requested detail collections).
• Update Routing / Update Reference / Attach File - The API response body, or { "success": true } when the API returns 204 No Content.

Example Usage & Common Use Cases

Get an Order with Items and Billing

Extensiv:
  Resource: Order
  Action: Get Order
  Order Id: {{ $json.orderId }}
  Order Detail: Order Items, Billing Details

Output: the order record with the requested collections

Get a Specific Item with Allocations

Extensiv:
  Resource: Order
  Action: Get Item
  Order Id: {{ $json.orderId }}
  Item Id: {{ $json.itemId }}
  Item Detail: Allocations With Detail

Output: the order item with allocation detail

Update Routing After Booking

[Book carrier] → [Extensiv]

Extensiv:
  Resource: Order
  Action: Update Routing
  Order Id: {{ $json.orderId }}
  Carrier: {{ steps.book.output.carrier }}
  SCAC Code: {{ steps.book.output.scac }}
  Tracking Number: {{ steps.book.output.tracking }}

Output: { success: true }

Set Custom References

Extensiv:
  Resource: Order
  Action: Update Reference
  Order Id: {{ $json.orderId }}
  Reference Collection:
    - Name: PO       Value: {{ $json.poNumber }}
    - Name: SO       Value: {{ $json.soNumber }}

Output: { success: true }

Attach a Document to an Order

[PDF Converter: build label] → [Extensiv]

Extensiv:
  Resource: Order
  Action: Attach File
  Order Id: {{ $json.orderId }}
  File: {{ steps.label.output }}

Output: attach response (or { success: true })

How It Works

1. Load the credential - The Extensiv credential is required; the operation fails without it.
2. Authenticate - The node exchanges the Client ID/Secret (Basic auth) plus the Login for an access token at /AuthServer/api/token (client-credentials grant).
3. Build the request - Calls the API at the base URL (default https://secure-wms.com) with Authorization: Bearer <token>, routing to the endpoint for the selected action.
4. Send - GET for reads; PUT for routing/reference updates (sending only the fields you provided); POST for document upload (streaming the file from workflow storage).
5. Return - The API response body is returned, or { success: true } on a 204 response.

Best Practices

• Store all credential fields - Client ID, Client Secret, and Login are all required; keep them in the credential.
• Request only the detail you need - Use Order Detail / Item Detail to pull just the sub-collections required, rather than always selecting All.
• Send only the routing fields you intend to change - Update Routing omits empty fields, so leave fields blank to leave them untouched.
• Confirm 204 handling - Update/attach operations may return 204 No Content; the node surfaces this as { success: true }, so branch on that rather than expecting a body.

Troubleshooting

Common Issues

• "Credential ID is required" - No credential was attached to the node. Add an Extensiv credential.
• "Order ID is required" - An order-scoped action was run without Order Id.
• "File is required" - Attach File was run without a File reference.
• Authentication failures - Verify Client ID/Secret and Login; confirm the OAuth client is enabled for the 3PL Warehouse Manager API.
• 404 on get/update - Confirm the Order Id (and Item Id for Get Item) exist and belong to the authenticated account.

Debugging Tips

• Verify auth independently - Confirm a token can be obtained from /AuthServer/api/token with your client credentials before debugging an operation.
• Start with Get Order - A simple Get Order confirms connectivity and credentials before attempting updates.

Related

• HTTP Request - For Extensiv endpoints not covered by this node
• Set - Shape values before an Update Routing / Update Reference call