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 perform validation and cleansing of various data types. Specifically, for the "Validate LEI Number" operation under the "Validation & Cleansing" resource, it validates Legal Entity Identifier (LEI) numbers. LEI numbers are unique identifiers assigned to legal entities participating in financial transactions globally.
Use cases include:
- Verifying the authenticity and correctness of LEI numbers before processing financial or regulatory data.
- Ensuring compliance with financial regulations by validating entity identifiers.
- Cleaning datasets containing LEI numbers to avoid errors in downstream systems.
For example, a user can input an LEI number into this node to confirm if it is valid and correctly formatted according to the Bedrijfsdata API's validation rules.
Properties
| Name | Meaning |
|---|---|
| Legal Entity Identifiers (LEI) Number | The LEI number string to validate. This is a required field where you enter the LEI to be checked. |
Output
The node outputs JSON data representing the validation result returned from the Bedrijfsdata API's /lei endpoint. This typically includes information about whether the LEI number is valid, possibly additional metadata about the LEI, and any error messages if invalid.
The output structure will be the direct response from the API call and may contain fields such as:
- Validation status (valid/invalid)
- Details about the LEI entity (if valid)
- Error or warning messages (if invalid)
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires configuration of an API authentication credential (an API key or token) within n8n to authorize requests.
- The base URL used for requests is
https://api.bedrijfsdata.nl/v1.2.
Troubleshooting
Common issues:
- Invalid or malformed LEI numbers will result in validation failure.
- Network connectivity problems or incorrect API credentials will cause request failures.
- Unexpected API responses or downtime on the Bedrijfsdata service may lead to errors.
Error messages:
- Errors thrown by the node will indicate if the API request failed or if the response was unexpected.
- If the LEI number is missing or empty, the node will not proceed due to the required property constraint.
- Messages like "Failed to fetch cities" or similar are unrelated to this operation but indicate how errors are reported generally.
Resolution tips:
- Ensure the LEI number is correctly formatted and complete.
- Verify that the API credential is correctly set up and has necessary permissions.
- Check network access and Bedrijfsdata API status.
- Review error messages for specific details and adjust inputs accordingly.
Links and References
- Legal Entity Identifier (LEI) Overview
- Bedrijfsdata API Documentation (for detailed API endpoints and responses)
- n8n Documentation (for general usage of custom nodes and credentials)