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 allows you to add shipments to an existing batch in the Shippo system. It is useful for managing multiple shipments collectively, such as when preparing a group of parcels for dispatch or organizing shipments for bulk processing. For example, if you have several shipments ready to be sent out and want to consolidate them under one batch for easier tracking and label generation, this operation facilitates that by adding shipment details to a specified batch.
Properties
| Name | Meaning |
|---|---|
| Batch Id | The unique identifier (Object ID) of the batch to which shipments will be added. This is required to specify the target batch. |
| SHIPPO API VERSION | Optional header string to specify a non-default version of the Shippo API to use for the request. Useful if you need to access features or behaviors specific to a particular API version. |
| Body | JSON object containing detailed shipment information to add to the batch. This includes nested fields such as addresses (from, to, return), customs declarations, carrier accounts, parcels with extra details like COD and insurance, and various shipment-specific metadata. |
Output
The output of this operation is a JSON object representing the updated batch with the newly added shipments included. The structure reflects the batch's current state after modification, typically including shipment details, batch metadata, and status information.
If binary data is returned (not indicated here), it would generally represent files such as shipping labels or manifests, but this operation primarily deals with JSON shipment data.
Dependencies
- Requires an active connection to the Shippo API.
- An API key credential for authenticating requests to Shippo must be configured in n8n.
- The base URL for API requests is
https://api.goshippo.com. - Optionally, the user can specify a custom API version via the
SHIPPO API VERSIONproperty.
Troubleshooting
- Invalid Batch Id: If the provided batch ID does not exist or is malformed, the API will likely return an error indicating the batch was not found. Verify the batch ID before making the request.
- Malformed JSON Body: The body must be valid JSON matching the expected schema. Errors may occur if required shipment fields are missing or incorrectly formatted.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- API Version Issues: Specifying an unsupported or deprecated API version might cause unexpected errors. Use the default or verify supported versions from Shippo documentation.
- Network or Rate Limits: Network connectivity issues or exceeding Shippo API rate limits can cause failures; check network status and API usage quotas.