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 integrates with the Shippo API to create a new address record. It is useful in workflows where you need to standardize, validate, or store shipping addresses before processing shipments or generating labels. For example, an e-commerce automation could use this node to verify customer addresses and ensure they are formatted correctly for carriers.
Properties
| Name | Meaning |
|---|---|
| SHIPPO API VERSION | Optional string to specify a non-default Shippo API version to use for the request. See Shippo's API versioning guide for details. |
Output
The node outputs JSON data representing the created address object as returned by the Shippo API. This typically includes standardized address fields such as name, street address, city, state, postal code, country, and validation status. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the Shippo API.
- The node sends requests to
https://api.goshippo.com. - Optionally supports specifying a custom API version via the
SHIPPO API VERSIONheader.
Troubleshooting
- Invalid API Key or Authentication Errors: Ensure that the API key credential is correctly configured and has the necessary permissions.
- Address Validation Failures: If the address data is incomplete or invalid, the Shippo API may return errors or warnings. Verify input address fields before sending.
- Unsupported API Version: Specifying an incorrect or unsupported API version string in the
SHIPPO API VERSIONproperty may cause request failures. Refer to Shippo’s API versioning documentation to select valid versions. - Network Issues: Connectivity problems can prevent successful API calls. Check network access and proxy settings if applicable.