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 details of a specific customs declaration. It is useful in logistics, e-commerce, and shipping workflows where users need to fetch detailed information about customs declarations associated with shipments. For example, an e-commerce platform can use this node to automatically pull customs declaration data for international orders to verify shipment contents or compliance.
Properties
| Name | Meaning |
|---|---|
| Customs Declaration Id | The unique identifier (object ID) of the customs declaration you want to retrieve. This is required. |
| Page | Optional page number to select when retrieving paginated results. Defaults to 1. |
| SHIPPO API VERSION | Optional header string to specify a non-default version of the Shippo API to use for the request. |
Output
The node outputs JSON data representing the customs declaration details retrieved from the Shippo API. This typically includes all metadata and fields related to the customs declaration object such as contents, value, currency, origin country, and other relevant customs information.
No binary data output is indicated by the source code or properties.
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
- Invalid or missing Customs Declaration Id: The node requires a valid customs declaration ID; ensure this is provided and correct.
- Authentication errors: Verify that the Shippo API key credential is correctly set up and has necessary permissions.
- API version issues: If using a custom API version header, ensure the version string is valid per Shippo's API versioning documentation.
- Pagination: If expecting multiple results, check the
pageparameter to navigate through pages properly.
Common error messages will likely come from the Shippo API and include HTTP status codes like 401 (Unauthorized), 404 (Not Found if the ID does not exist), or 400 (Bad Request for invalid parameters).