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 transaction by its unique identifier. It is useful in scenarios where you need to fetch shipping transaction information such as tracking, status, or cost after creating or managing shipments through Shippo. For example, after creating a shipment label, you might want to get the transaction details to confirm the purchase or track the package.
Properties
| Name | Meaning |
|---|---|
| Transaction Id | The unique object ID of the transaction you want to retrieve from Shippo. This is required to identify the transaction. |
| SHIPPO API VERSION | Optional header string to specify a non-default version of the Shippo API to use for this request. Useful for compatibility or testing different API versions. |
Output
The node outputs JSON data representing the full details of the requested transaction. This typically includes fields such as transaction status, tracking number, shipping cost, carrier information, and any metadata associated with the transaction. There is no binary output.
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 Transaction Id: Ensure the Transaction Id provided is correct and exists in your Shippo account.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- API version issues: If using the optional API version header, ensure the version string matches one supported by Shippo; otherwise, the request may fail.
- Network or connectivity problems: Confirm that n8n can reach the Shippo API endpoint without firewall or proxy issues.