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 register a new carrier account. It allows users to provide carrier-specific details and parameters to create or link a carrier account within Shippo's system. This is useful for businesses that manage multiple shipping carriers and want to automate the registration process directly from their workflow.
Practical examples include:
- Automatically registering a new carrier account when onboarding a new shipping provider.
- Managing multiple carrier accounts programmatically without manual entry in the Shippo dashboard.
- Integrating carrier account registration as part of a larger shipping or order fulfillment automation.
Properties
| Name | Meaning |
|---|---|
| SHIPPO API VERSION | Optional string to specify a non-default Shippo API version to use for the request. Useful for compatibility with different API versions. |
| Carrier | The name or identifier of the carrier to register (e.g., USPS, FedEx). |
| Parameters | A JSON object containing additional parameters required by the carrier for registration. This can include credentials, account numbers, or other carrier-specific data. |
Output
The node outputs JSON data representing the response from the Shippo API after attempting to register the carrier account. This typically includes details about the newly registered carrier account such as its ID, status, and any metadata returned by Shippo.
If the API supports it, binary data output is not indicated in this implementation.
Dependencies
- Requires an active Shippo API key credential configured in n8n to authenticate requests.
- Depends on the Shippo REST API endpoint at
https://api.goshippo.com. - Optionally uses a custom API version header if specified.
Troubleshooting
- Invalid API Key or Authentication Errors: Ensure the Shippo API key credential is correctly set up and has the necessary permissions.
- Malformed Parameters JSON: The
Parametersfield expects valid JSON. Invalid JSON will cause parsing errors. Validate JSON syntax before input. - Unsupported Carrier Name: If the carrier name is incorrect or unsupported by Shippo, the API may return an error. Verify carrier names against Shippo documentation.
- API Version Issues: Specifying an unsupported or deprecated API version in
SHIPPO API VERSIONmay lead to unexpected errors. Use the default or consult Shippo’s API versioning guide.