Actions12
Overview
The "Create SE-USPS Label" operation in the Shipentegra node allows users to generate shipping labels specifically for USPS shipments within the Shipentegra platform. This operation is useful for e-commerce businesses, logistics providers, or any users who need to automate the creation of USPS shipping labels with detailed shipment and customs information.
Typical use cases include:
- Automating label generation for orders shipped via USPS.
- Integrating USPS label creation into order fulfillment workflows.
- Managing declared items and customs details for international shipments.
- Specifying sender information and package details programmatically.
For example, an online store could use this node to automatically create USPS shipping labels when an order is ready to ship, including all necessary customs declarations and sender details.
Properties
| Name | Meaning |
|---|---|
| Special Service | A string specifying any special service required for the shipment. |
| Order ID | Numeric identifier of the order associated with the label. |
| Store ID | Numeric identifier of the store from which the shipment originates. |
| Number | A string representing a reference number related to the shipment (e.g., tracking or internal reference). |
| Verpackg | Boolean flag indicating whether packaging is included or required. |
| Content | Description of the shipment content. |
| Weight | Numeric weight of the shipment (units not specified but typically grams or kilograms). |
| IOSS Number | String representing the Import One-Stop Shop (IOSS) number used for EU VAT compliance on imports. |
| Currency | Currency code for declared item prices and values. Options include standard ISO currency codes such as USD, EUR, GBP, JPY, etc., plus a "None" option for no currency specified. |
| Items | Collection of declared items in the shipment. Each item includes: - Item ID (number) - Declared Quantity (number) - Declared Price (number) - GTIP (string, likely a customs tariff code) |
| Ship From | Sender address information including: - Name (required) - Address 1 (required) - Address 2 (optional) - State (optional) - City (required) - Zip Code (optional) - Phone (optional) |
Output
The node outputs JSON data containing the response from the Shipentegra API after attempting to create the USPS shipping label. This typically includes label details such as label URLs, tracking numbers, shipment status, and any metadata returned by the API.
If the API returns binary data (e.g., PDF or image of the label), it would be handled accordingly, but based on the provided information, the output focuses on JSON responses describing the created label.
Dependencies
- Requires an API key credential for authenticating with the Shipentegra API.
- The node communicates with the Shipentegra public API endpoint at
https://publicapi.shipentegra.com/v1. - Proper configuration of the API credentials in n8n is necessary.
- The user must ensure that the Shipentegra account has permissions and setup to create USPS labels.
Troubleshooting
- Invalid or missing API credentials: Ensure the API key credential is correctly configured and active.
- Missing required fields: Required fields such as sender name, address line 1, city, and declared item details must be provided; otherwise, the API may reject the request.
- Incorrect currency codes: Use valid ISO currency codes from the provided options; invalid codes may cause errors.
- API errors related to shipment details: Verify that weights, quantities, and prices are within allowed ranges and formats.
- Network or connectivity issues: Confirm that the n8n instance can reach the Shipentegra API endpoint.
Common error messages might include authentication failures, validation errors for input data, or quota limits exceeded. Reviewing the API response message will help identify the exact issue.
Links and References
- Shipentegra API Documentation (general reference for API capabilities)
- USPS Shipping Guidelines (for understanding USPS label requirements)
- IOSS VAT Information (for details on IOSS number usage)
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.