Actions30
- Company Actions
- Company (Related) Actions
- Data (Advanced) Actions
- Enrich Actions
- Live Web RAG Actions
- LLM Template Actions
- Other Data Actions
- Validation & Cleansing Actions
Overview
This node integrates with the Bedrijfsdata API to validate Dutch Chamber of Commerce (KvK) numbers. It sends a request to the API endpoint dedicated to KvK number validation and returns the validation result. This is useful in scenarios where you need to verify the authenticity or correctness of a KvK number before processing it further, such as during customer onboarding, data cleansing, or compliance checks.
Practical examples:
- Validating user-submitted KvK numbers in a form to ensure they are correct.
- Cleaning up a database of company records by verifying stored KvK numbers.
- Automating workflows that require confirmation of valid business registrations.
Properties
| Name | Meaning |
|---|---|
| Kamer Van Koophandel (KvK) Number | (Required) The KvK number to validate. This should be a string representing the KvK number. |
Output
The node outputs JSON data containing the response from the Bedrijfsdata API about the KvK number validation. The exact structure depends on the API response but typically includes fields indicating whether the KvK number is valid, possibly additional metadata about the company associated with the KvK number, or error information if invalid.
No binary data output is involved.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires an API key credential configured in n8n for authentication with the Bedrijfsdata service.
- Network access to
https://api.bedrijfsdata.nl/v1.2must be available.
Troubleshooting
Common issues:
- Invalid or missing KvK number input will cause the API to return errors.
- Network connectivity problems can prevent successful API calls.
- Incorrect or expired API credentials will lead to authentication failures.
Error messages:
- Errors related to API request failures will include messages like "Failed to fetch cities" or "Unexpected API response," which indicate issues with the external service or malformed requests.
- Authentication errors usually indicate misconfigured or missing API keys.
Resolutions:
- Ensure the KvK number is correctly formatted and provided.
- Verify API credentials are correctly set up in n8n.
- Check network connectivity and API service status.
Links and References
- Bedrijfsdata API Documentation (general reference for API endpoints)
- KvK Official Website for understanding KvK numbers and their format