Skip to content
For LLMsView as Markdown·

UPS ​

undefined

DetailValue
CategoryLogistics
Base URLhttps://onlinetools.ups.com/api
AuthenticationOAuth2 Client Credentials
Endpoints7
Connector keyups

Using UPS in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick UPS from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET Tracking
GET Rates
GET Shipments
GET Address Validation
GET Time in Transit
GET Pickup
GET Locations

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

Tracking

DetailValue
Operation IDtracking_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select tracking_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Rates

DetailValue
Operation IDrates_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select rates_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Shipments

DetailValue
Operation IDshipments_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select shipments_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Address Validation

DetailValue
Operation IDaddress_validation_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select address_validation_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Time in Transit

DetailValue
Operation IDtime_in_transit_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select time_in_transit_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Pickup

DetailValue
Operation IDpickup_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select pickup_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.

GET ​

Locations

DetailValue
Operation IDlocations_6
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your UPS connection from the Connection dropdown.
  3. In the Operation dropdown, select locations_6.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream UPS API reference.