Appearance
UPS
undefined
| Detail | Value |
|---|---|
| Category | Logistics |
| Base URL | https://onlinetools.ups.com/api |
| Authentication | OAuth2 Client Credentials |
| Endpoints | 7 |
| Connector key | ups |
Using UPS in a workflow
- Go to Connections and click New Connection.
- Pick UPS from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | tracking_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
tracking_0. - 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
| Detail | Value |
|---|---|
| Operation ID | rates_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
rates_1. - 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
| Detail | Value |
|---|---|
| Operation ID | shipments_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
shipments_2. - 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
| Detail | Value |
|---|---|
| Operation ID | address_validation_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
address_validation_3. - 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
| Detail | Value |
|---|---|
| Operation ID | time_in_transit_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
time_in_transit_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
| Detail | Value |
|---|---|
| Operation ID | pickup_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
pickup_5. - 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
| Detail | Value |
|---|---|
| Operation ID | locations_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your UPS connection from the Connection dropdown.
- In the Operation dropdown, select
locations_6. - 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.