Actions12
Overview
This node integrates with the Shipentegra API to create a SE-UPS shipping label. It is designed for logistics and e-commerce workflows where users need to generate UPS labels for shipments, including customs and item declaration details. Typical use cases include automating label creation for orders in online stores or warehouses, streamlining shipping processes, and ensuring compliance with international shipping regulations.
For example, an e-commerce platform can use this node to automatically generate UPS labels with declared items and sender information when an order is ready to ship, reducing manual entry and errors.
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 shipment (minimum 1). |
| Store ID | Numeric identifier of the store from which the shipment originates (minimum 1). |
| Number | A string representing a reference number related to the shipment. |
| Verpackg | Boolean flag indicating packaging status or type (true/false). |
| Content | Description of the shipment content as a string. |
| Weight | Numeric weight of the shipment (minimum 0). |
| IOSS Number | String representing the Import One-Stop Shop number for VAT purposes in EU shipments. |
| Currency | Currency code for declared prices; options include standard ISO currency codes such as EUR, USD, GBP, etc., plus "None" 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 creating the SE-UPS label. This typically includes label details such as tracking numbers, label URLs or encoded label data, shipment confirmation, and any metadata returned by the API.
If the API returns binary label data (e.g., PDF or image), it would be included in the output as binary data, representing the actual shipping label file ready for printing or storage.
Dependencies
- Requires an API key credential for authenticating with the Shipentegra API.
- The node uses the Shipentegra public API endpoint at
https://publicapi.shipentegra.com/v1. - Proper configuration of the API authentication token in n8n credentials is necessary.
- The API expects JSON requests and responses with UTF-8 encoding.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Invalid or incomplete sender address fields (e.g., missing required city or name) may result in validation errors.
- Incorrect currency codes or unsupported currencies could lead to request rejection.
- Declared items must have valid quantities and prices; missing these may cause errors.
- Weight must be a non-negative number; negative or missing values might trigger errors.
Error messages:
- Authentication errors: Check that the API key credential is correctly set up and has proper permissions.
- Validation errors: Review the input properties for required fields and correct formats.
- API rate limits or server errors: Retry after some time or check API status.
Links and References
- Shipentegra API Documentation (assumed base URL)
- UPS Shipping Label Guidelines (for understanding label requirements)
- International shipping customs declaration standards (for item declarations and IOSS number usage)