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 validates an IBAN (International Bank Account Number) by sending the provided IBAN number to the Bedrijfsdata API's validation endpoint. It is useful in scenarios where you need to verify the correctness and format of IBAN numbers before processing payments, onboarding customers, or performing financial audits. For example, a business automation workflow could use this node to ensure that bank account details entered by users are valid IBANs, reducing errors in payment processing.
Properties
| Name | Meaning |
|---|---|
| IBAN Number | (Required) The IBAN number string to validate. Example: "NL91ABNA0417164300". |
Output
The node outputs the JSON response from the Bedrijfsdata API validation endpoint for the IBAN number. This typically includes fields indicating whether the IBAN is valid, possibly the country code, bank identifier, and other metadata related to the IBAN structure.
If the API supports it, the output may also include error messages or reasons why the IBAN is invalid.
The node does not output binary data.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires an API key credential configured in n8n for authenticating requests to the Bedrijfsdata service.
- The node makes a GET request to the
/ibanendpoint of the Bedrijfsdata API with the IBAN number as a query parameter.
Troubleshooting
Common Issues:
- Invalid or malformed IBAN input will result in validation failure.
- Network connectivity issues or incorrect API credentials can cause request failures.
- API rate limits might be reached if too many requests are sent in a short time.
Error Messages:
- Errors returned from the API will be surfaced as node operation errors with messages like "Failed to fetch cities" or "Unexpected API response," depending on the endpoint. For IBAN validation, similar errors may occur if the API response is unexpected or the IBAN is invalid.
- If the node throws an error about missing credentials, ensure the API key is properly set up in n8n.
- If the IBAN parameter is empty or missing, the node will not perform validation and may throw an error.
Resolution:
- Verify the IBAN number format before passing it to the node.
- Check API credentials and network connectivity.
- Review API usage limits and adjust workflow frequency accordingly.
Links and References
- IBAN Wikipedia
- Bedrijfsdata API Documentation (general reference; specific endpoint docs may require access)
- n8n Documentation on HTTP Request Nodes (for understanding API calls)
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.