Bedrijfsdata icon

Bedrijfsdata

Get data from the Bedrijfsdata API.
Join our community

Actions31

Overview

This node integrates with the Bedrijfsdata API to perform validation and cleansing of postcodes globally. Specifically, the "Validate Postcode" operation allows users to verify whether a given postcode is valid within a specified country using its ISO 3166-1 Alpha-2 code.

Common scenarios where this node is beneficial include:

  • Data quality assurance workflows where address data needs verification before further processing.
  • Customer onboarding processes requiring validation of postal codes to reduce errors in shipping or billing addresses.
  • Enriching datasets by confirming the correctness of geographic identifiers.

For example, a user can input a postcode like "1012 WX" and specify the country code "nl" (Netherlands) to check if the postcode exists and is correctly formatted according to Dutch postal standards.

Properties

Name Meaning
Postcode (Required) The postcode string to validate.
Country (ISO 3166-1 Alpha-2) (Required) The two-letter country code representing the country context for validation. Examples: "nl" for Netherlands, "us" for United States.

Output

The node outputs JSON data containing the validation result from the Bedrijfsdata API. This typically includes information about the validity of the postcode, possibly normalized or formatted versions, and any related metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Bedrijfsdata API service.
  • Requires configuration of an API authentication credential (an API key or token) within n8n to authorize requests to the Bedrijfsdata API.
  • Network access to https://api.bedrijfsdata.nl/v1.2 is necessary.

Troubleshooting

  • Invalid or missing API credentials: The node will fail if the API key/token is not set or invalid. Ensure that the API credential is properly configured in n8n.
  • Incorrect country code or postcode format: If the country code is not a valid ISO 3166-1 Alpha-2 code or the postcode does not conform to expected formats, the API may return errors or empty results. Verify inputs carefully.
  • Network issues: Connectivity problems to the Bedrijfsdata API endpoint will cause request failures. Check network settings and firewall rules.
  • API rate limits: Excessive requests might be throttled by the API provider. Review API usage policies and implement retry logic if needed.

Common error messages may include:

  • "Failed to fetch cities" or similar messages indicating unexpected API responses.
  • HTTP errors such as 401 Unauthorized (invalid credentials) or 429 Too Many Requests (rate limiting).

Resolving these usually involves checking credentials, input values, and network connectivity.

Links and References

Discussion