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 about a specific refund by its unique Refund Id. It is useful in scenarios where you need to verify the status, amount, or other metadata of a refund processed through Shippo's shipping and returns platform. For example, after initiating a refund, you can use this node to confirm that the refund was successfully created and obtain its current state.
Properties
| Name | Meaning |
|---|---|
| Refund Id | The unique identifier (Object ID) of the refund you want to retrieve information about. This is required to specify which refund to get. |
| SHIPPO API VERSION | Optional header string to specify a non-default version of the Shippo API to use for this request. Useful if you want to target a specific API version as per Shippo's versioning guide. |
Output
The node outputs JSON data representing the refund object retrieved from Shippo. This typically includes fields such as refund status, amount, currency, creation date, and related shipment or transaction details. The output structure directly reflects the Shippo API's refund response schema.
No binary data output is expected from this operation.
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 supports specifying the API version via a custom header.
Troubleshooting
- Missing or invalid Refund Id: The node requires a valid Refund Id; ensure it is correctly provided and corresponds to an existing refund.
- Authentication errors: Verify that the Shippo API key credential is correctly set up and has necessary permissions.
- API version issues: If specifying a custom API version, ensure it matches one supported by Shippo; otherwise, the request may fail.
- Network or connectivity problems: Confirm that your environment can reach the Shippo API endpoint without firewall or proxy restrictions.
Common error messages will generally come from the Shippo API and include HTTP status codes like 401 (Unauthorized), 404 (Refund not found), or 400 (Bad request). Resolving these involves checking credentials, input parameters, and API version compatibility.