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 Service Group. It allows users to modify details of a service group within their Shippo account, which is useful for managing shipping services and configurations programmatically. Typical use cases include automating updates to shipping options, adjusting service group parameters based on business rules, or synchronizing service group data from other systems.
Properties
| Name | Meaning |
|---|---|
| SHIPPO API VERSION | Optional string to specify a non-default version of the Shippo API to use for the request. This allows targeting specific API versions as per Shippo's versioning guide. |
Output
The node outputs JSON data representing the updated Service Group object returned by the Shippo API. This typically includes fields such as the service group's ID, name, and any updated attributes reflecting the changes made. The output does not include binary data.
Dependencies
- Requires an active Shippo API key credential configured in n8n for authentication.
- Connects to the Shippo REST API at
https://api.goshippo.com. - Optionally supports specifying a custom API version via the
SHIPPO API VERSIONheader.
Troubleshooting
- Authentication errors: Ensure that the Shippo API key credential is correctly set up and has sufficient permissions.
- Invalid API version: If specifying a custom API version, verify it matches one supported by Shippo; otherwise, requests may fail.
- Service Group not found: Confirm the Service Group ID exists and is accessible with the provided credentials.
- Network issues: Check connectivity to the Shippo API endpoint.