Actions68
- Parcels Actions
- Shipments Actions
- Rates Actions
- Transactions Actions
- Customs Items Actions
- Tracking Status Actions
- Batches Actions
- Orders Actions
- Pickups Actions
- Service Groups Actions
- Customs Declarations Actions
- Refunds Actions
- Manifests Actions
- Carrier Accounts Actions
- Webhooks Actions
- Carrier Parcel Templates Actions
- User Parcel Templates Actions
- Rates At Checkout Actions
- Shippo Accounts Actions
- Addresses Actions
Overview
This node interacts with the Shippo API to retrieve detailed information about a specific parcel. It is useful in workflows where you need to track or verify parcel details by their unique identifier, such as confirming shipment status, verifying parcel attributes before shipping, or integrating parcel data into other systems.
A practical example would be an e-commerce automation that fetches parcel details after an order is shipped to update the customer or internal tracking system.
Properties
| Name | Meaning |
|---|---|
| Parcel Id | The unique object ID of the parcel you want to retrieve information for. This is required. |
| SHIPPO API VERSION | Optional header to specify a non-default version of the Shippo API to use for this request. |
Output
The node outputs JSON data representing the full details of the requested parcel as returned by the Shippo API. This typically includes fields such as parcel dimensions, weight, metadata, and any other parcel-specific information provided by Shippo.
No binary data output is produced by this operation.
Dependencies
- Requires an active Shippo API key credential configured in n8n.
- Makes HTTP requests to the Shippo API endpoint at
https://api.goshippo.com. - Optionally supports specifying the API version via a custom header.
Troubleshooting
- Missing or invalid Parcel Id: Ensure the Parcel Id is correctly provided and corresponds to an existing parcel in Shippo.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- API version issues: If using the optional API version header, confirm the version string is supported by Shippo.
- Network or connectivity problems: Check network access to the Shippo API endpoint.
Common error messages will generally come from the Shippo API and may include 404 (parcel not found), 401 (unauthorized), or 400 (bad request). Resolving these involves checking input values, credentials, and API usage.