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 update an existing Shippo Account. It is useful when you need to modify account details programmatically within an n8n workflow, such as updating account settings or metadata without manual intervention. For example, you might automate updating your shipping account information based on changes in your CRM or ERP system.
Properties
| Name | Meaning |
|---|---|
| Shippo Account Id | The unique identifier (Object ID) of the Shippo Account you want to update. This is required to specify which account to modify. |
| SHIPPO API VERSION | Optional header 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. |
Output
The node outputs JSON data representing the updated Shippo Account object returned by the Shippo API. This typically includes all the account details after the update operation has been applied.
If the Shippo API supports binary data in responses (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is JSON only.
Dependencies
- Requires an active Shippo API key credential configured in n8n to authenticate requests.
- Connects to the Shippo API endpoint at
https://api.goshippo.com. - Optionally uses the
SHIPPO-API-VERSIONHTTP header to specify API versioning.
Troubleshooting
- Invalid Shippo Account Id: If the provided account ID does not exist or is malformed, the API will return an error. Verify the ID before running the node.
- Authentication errors: Ensure that the API key credential is valid and has sufficient permissions.
- Unsupported API version: If specifying
SHIPPO-API-VERSION, ensure the version string matches one supported by Shippo; otherwise, the request may fail. - Network issues: Connectivity problems to the Shippo API endpoint can cause timeouts or failures.