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 operation deletes a specific Service Group in the Shippo system by its unique identifier. It is useful when you need to remove outdated or incorrect service groups from your Shippo account programmatically. For example, if you manage multiple shipping configurations and want to clean up unused service groups automatically, this operation allows you to do so efficiently.
Properties
| Name | Meaning |
|---|---|
| Service Group Id | The unique object ID of the service group you want to delete. This is required to identify which group to remove. |
| SHIPPO API VERSION | Optional header to specify a non-default version of the Shippo API to use for this request. Useful for compatibility with different API versions. |
Output
The output JSON will typically contain the response from the Shippo API confirming the deletion of the specified service group. This may include status information or confirmation messages. The node does not output binary data.
Dependencies
- Requires an active Shippo API key credential configured in n8n.
- Connects to the Shippo REST API at
https://api.goshippo.com. - Optionally supports specifying the API version via a custom header.
Troubleshooting
- Invalid Service Group Id: If the provided ID does not exist or is malformed, the API will return an error indicating the service group could not be found. Verify the ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
- API Version Issues: Specifying an unsupported API version may lead to unexpected errors. Use the default or verify supported versions in Shippo’s documentation.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network access to the Shippo API endpoint.