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 update an existing user parcel template. It is useful when you need to modify the details of a parcel template that a user has previously created, such as changing dimensions, weight, or other parcel attributes stored in the template. This operation helps automate parcel management workflows by programmatically updating templates without manual intervention.
Practical examples include:
- Automatically adjusting parcel templates based on updated packaging standards.
- Synchronizing parcel template data from an external system into Shippo.
- Bulk updating multiple user parcel templates via automation.
Properties
| Name | Meaning |
|---|---|
| User Parcel Template Object Id | The unique identifier (Object ID) of the user parcel template you want to update. This is required. |
| SHIPPO API VERSION | Optional header to specify a non-default version of the Shippo API to use for this request. See Shippo's API versioning guide for details. |
Output
The node outputs JSON data representing the updated user parcel template as returned by the Shippo API. This typically includes all the fields of the parcel template after the update, such as dimensions, weight, and any metadata associated with the template.
If the API supports binary data output (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON responses.
Dependencies
- Requires an active Shippo API key credential configured in n8n to authenticate requests.
- Depends on the Shippo REST API endpoint
https://api.goshippo.com. - Optionally uses the
SHIPPO-API-VERSIONHTTP header to select a specific API version.
Troubleshooting
- Invalid Object ID: If the provided User Parcel Template Object Id does not exist or is malformed, the API will return an error indicating the resource was not found. Verify the Object ID is correct.
- Authentication errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- API version issues: Specifying an unsupported or incorrect API version in the
SHIPPO-API-VERSIONheader may lead to unexpected errors. Use the default or verify supported versions via Shippo documentation. - Network or connectivity problems: Ensure your environment can reach
https://api.goshippo.com.