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 create shipping manifests. A manifest is a document listing all shipments being sent out, which helps in organizing and tracking multiple packages collectively. This operation is useful for e-commerce businesses or logistics providers who need to batch shipments into manifests for easier management and compliance with carrier requirements.
Practical examples include:
- Generating a daily manifest of all orders shipped from a warehouse.
- Creating manifests to submit to carriers for pickup scheduling.
- Automating the creation of manifests after generating multiple shipping labels.
Properties
| Name | Meaning |
|---|---|
| SHIPPO API VERSION | Optional string to specify a non-default version of the Shippo API to use for this request. See Shippo's API versioning guide. |
Output
The node outputs JSON data representing the created manifest as returned by the Shippo API. This typically includes details such as the manifest ID, status, associated shipments, creation timestamp, and any relevant metadata.
If the API supports binary data (e.g., PDF manifest documents), the node would provide that as binary output; however, based on the provided code and properties, only JSON output is expected here.
Dependencies
- Requires an active Shippo API key credential configured in n8n for authentication.
- Connects to the Shippo API endpoint at
https://api.goshippo.com. - Optionally uses the
SHIPPO-API-VERSIONheader if specified to select a particular API version.
Troubleshooting
- Invalid API Key or Authentication Errors: Ensure the Shippo API key credential is correctly set up and has necessary permissions.
- Unsupported API Version: If specifying
SHIPPO API VERSION, verify the version string matches one supported by Shippo; otherwise, the request may fail. - Network or Connectivity Issues: Confirm that n8n can reach the Shippo API endpoint without firewall or proxy restrictions.
- Malformed Request Data: Check that all required fields for creating a manifest are properly provided in preceding nodes or input data.