Actions17
- Shipping Status Actions
- Confirming Actions
- Labelling Actions
- Shipment Actions
- Barcode Actions
- Checkout Actions
- Deliverydate Actions
- Locations Actions
- Postalcode Check Actions
- Timeframes Actions
Overview
This node interacts with the PostNL API to retrieve the signature associated with a shipment. Specifically, the "Get Shipment Signature" operation under the "Shipping Status" resource allows users to obtain proof of delivery by fetching the signature image or data linked to a shipment barcode.
Common scenarios where this node is beneficial include:
- Verifying that a package was delivered and signed for by the recipient.
- Automating delivery confirmation workflows in logistics or e-commerce systems.
- Archiving or displaying shipment signatures for customer service or auditing purposes.
For example, an e-commerce platform can use this node to automatically fetch and store the signature image once a package is marked as delivered, enabling customer support to quickly access proof of delivery if needed.
Properties
| Name | Meaning |
|---|---|
| Barcode | Barcode of the shipment; a string identifier used to specify which shipment's signature to retrieve. Example: "3SDEVC172649258" |
Output
The node outputs JSON data containing the shipment signature information retrieved from the PostNL API. This typically includes:
- The signature image or encoded data proving delivery.
- Metadata related to the shipment and signature (e.g., timestamp, signer details).
If the signature is returned as binary data (such as an image), it will be available in the binary output field, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an active connection to the PostNL API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the API is set dynamically based on the environment credential configuration.
Troubleshooting
- Invalid Barcode: If the barcode provided does not correspond to any shipment, the API may return an error or empty result. Verify the barcode value is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- Network Issues: Connectivity problems with the PostNL API endpoint can cause request timeouts or failures. Check network access and API availability.
- Unexpected Response Format: If the API changes its response structure, the node might fail to parse the signature data properly. Confirm compatibility with the current API version.
Links and References
- PostNL Developer Portal – Official documentation and API references.
- PostNL API Authentication – Details on obtaining and using API keys.
- n8n Documentation – General guidance on creating and using custom nodes.