Actions12
Overview
The node integrates with the Shipentegra API to create a SE-DHL Ecommerce shipping label. This operation is useful for e-commerce businesses or logistics providers who need to generate DHL shipping labels for their orders programmatically. By automating label creation, users can streamline their shipping workflows, reduce manual errors, and improve operational efficiency.
Typical use cases include:
- Automatically generating DHL ecommerce labels when an order is placed.
- Integrating label creation into a larger fulfillment automation workflow.
- Managing multiple shipments with detailed item declarations and sender information.
Properties
| Name | Meaning |
|---|---|
| Special Service | A string specifying any special service required for the shipment. |
| Order ID | Numeric identifier of the order for which the label is being created. |
| Store ID | Numeric identifier of the store associated with the order. |
| Number | A string representing a reference number related to the shipment. |
| Verpackg | Boolean indicating whether packaging is included (true/false). |
| Content | Description of the shipment content as a string. |
| Weight | Numeric weight of the shipment. |
| IOSS Number | String representing the Import One-Stop Shop number for tax purposes. |
| Currency | Currency code for declared values; options include standard ISO currency codes like EUR, USD, GBP, etc., plus "None". |
| 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 | |
| - State | |
| - City (required) | |
| - Zip Code | |
| - Phone |
Output
The node outputs JSON data containing the response from the Shipentegra API after creating the DHL ecommerce label. This typically includes label details such as tracking numbers, label URLs or files, shipment status, and other metadata returned by the API.
If binary data (such as PDF label files) is returned, it will be provided accordingly, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the Shipentegra API.
- The base URL used is
https://publicapi.shipentegra.com/v1. - The node expects JSON content-type headers and supports localization via an optional language setting in credentials.
Troubleshooting
- Invalid or missing API credentials: Ensure that a valid API key or authentication token is configured in the node credentials.
- Missing required fields: Required properties such as Order ID, Store ID, and mandatory Ship From address fields must be provided; otherwise, the API may reject the request.
- Incorrect currency codes: Use valid ISO currency codes from the provided list; invalid codes may cause errors.
- API rate limits or downtime: If requests fail repeatedly, check Shipentegra API status and ensure you are not exceeding rate limits.
- Malformed item declarations: Each declared item must have valid numeric IDs, quantities, and prices; incorrect data types or missing values can cause failures.
Links and References
- Shipentegra API Documentation (assumed base URL)
- ISO Currency Codes Reference: https://www.iso.org/iso-4217-currency-codes.html