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 address by its unique identifier. It is useful in scenarios where you need to fetch validated address data, verify shipping destinations, or enrich order information with accurate address details. For example, an e-commerce workflow could use this node to confirm customer shipping addresses before generating shipping labels.
Properties
| Name | Meaning |
|---|---|
| Address Id | The unique object ID of the address you want to retrieve from Shippo. This is required to specify which address to get. |
| SHIPPO API VERSION | Optional header to specify a non-default version of the Shippo API to use for the request. Useful for compatibility with different API versions. |
Output
The node outputs JSON data representing the full details of the requested address as returned by the Shippo API. This typically includes fields such as the recipient's name, street address, city, state, postal code, country, and validation status. There is no binary output.
Dependencies
- Requires an active Shippo API key credential configured in n8n.
- The node 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 Address Id: Ensure the Address Id property is provided and corresponds to a valid address in your Shippo account.
- Authentication errors: Verify that the Shippo API key credential is correctly set up and has necessary permissions.
- API version issues: If using the optional API version header, ensure the specified version string matches a supported Shippo API version.
- Network or connectivity problems: Confirm that your environment can reach the Shippo API endpoint without firewall restrictions.