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 perform a postal code validation and lookup operation called "Checkout Postalcode Check." It verifies the combination of a postal code, house number, and optional house number addition to confirm address details or retrieve related information. This is useful in e-commerce checkout flows, address verification processes, or any scenario where validating Dutch postal addresses is required.
For example, an online store can use this node to validate customer shipping addresses before finalizing orders, reducing delivery errors and improving logistics efficiency.
Properties
Name | Meaning |
---|---|
Postalcode | The postal code to check (e.g., "3571ZZ"). |
Housenumber | The house number associated with the postal code (e.g., "74"). |
Housenumberaddition | An optional addition to the house number (e.g., "bis"), used for more precise addressing. |
Output
The node outputs JSON data containing the response from the PostNL API regarding the postal code check. This typically includes validated address details or status information confirming whether the postal code and house number combination is valid.
If the API returns binary data (not indicated here), it would represent raw response content such as documents or images, but this node primarily deals with JSON responses.
Dependencies
- Requires an active PostNL API key credential configured in n8n.
- The node uses the PostNL API endpoint specified by the environment URL provided in the credentials.
- The node depends on the
@devlikeapro/n8n-openapi-node
package for OpenAPI integration.
Troubleshooting
- Invalid postal code or house number: If the API returns an error indicating invalid input, verify that the postal code and house number are correct and formatted properly.
- Authentication errors: Ensure the API key credential is correctly set up and has the necessary permissions.
- Network issues: Confirm that the n8n instance can reach the PostNL API endpoint without firewall or proxy restrictions.
- Missing required parameters: Both postal code and house number are mandatory; omitting them will cause errors.