Actions31
- 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 BIC (Bank Identifier Code) numbers. It sends a request to the API endpoint dedicated to BIC validation and returns the validation result. This is useful in scenarios where you need to verify the correctness of BIC numbers for banking, financial transactions, or data cleansing purposes.
Practical examples include:
- Validating BIC numbers entered by users in forms before processing payments.
- Cleansing datasets containing bank details to ensure all BICs are valid.
- Automating workflows that require confirmation of bank identifiers for compliance or reporting.
Properties
| Name | Meaning |
|---|---|
| BIC Number | (Required) Enter a BIC number to validate. The node will check if this BIC number is valid. |
Output
The node outputs JSON data representing the response from the Bedrijfsdata API's BIC validation endpoint. The structure typically includes fields indicating whether the BIC number is valid and may contain additional metadata about the BIC.
If the node supports binary output, it would be related to any raw data returned by the API, but based on the static code, the primary output is JSON validation results.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Needs an API key credential configured in n8n for authentication with the Bedrijfsdata service.
- The base URL used for requests is
https://api.bedrijfsdata.nl/v1.2. - The node uses HTTP GET requests to the
/bicendpoint with the BIC number as a query string parameter.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an empty or malformed BIC number will likely result in an error or invalid response.
- Network connectivity problems can prevent reaching the Bedrijfsdata API.
Error messages:
- Errors from the API such as "Failed to fetch cities" or unexpected responses indicate issues with the request or API availability.
- Node operation errors thrown when the API response is not as expected suggest checking the input BIC number and API status.
Resolutions:
- Ensure the API key credential is correctly set up and has necessary permissions.
- Validate the format of the BIC number before sending it to the node.
- Check network connectivity and Bedrijfsdata API status if errors persist.
Links and References
- Bedrijfsdata API Documentation (general reference for API endpoints)
- BIC (SWIFT) Codes Explanation (background on BIC codes)
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.