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
The node integrates with the Bedrijfsdata API to perform various data retrieval and validation tasks. Specifically, for the Validation & Cleansing resource with the Validate URL operation, it validates URLs by sending them to the API and receiving validation results. This is useful in workflows where you need to ensure that URLs are correctly formatted and valid before further processing or storage.
Practical examples:
- Validating user-submitted URLs in a form before saving them.
- Cleaning and verifying URLs in a dataset during an ETL process.
- Ensuring URLs used in marketing campaigns are valid to avoid broken links.
Properties
| Name | Meaning |
|---|---|
| URL | (Required) Enter a URL string to validate. The node sends this URL to the API to check its validity. |
Output
The node outputs JSON data containing the validation results from the Bedrijfsdata API for the provided URL. The exact structure depends on the API response but typically includes fields indicating whether the URL is valid, any errors found, and possibly normalized or parsed URL components.
No binary data output is involved in this operation.
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.2is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an empty or malformed URL string may result in API errors or validation failure.
- Network connectivity problems can prevent reaching the API endpoint.
Error messages:
- Errors related to API request failures will be thrown as node operation errors with messages indicating the problem (e.g., "Failed to fetch cities" in other operations suggests similar error handling).
- If the API returns unexpected responses, the node throws descriptive errors to help diagnose issues.
Resolution tips:
- Ensure the API key credential is correctly set up and has sufficient permissions.
- Validate input URLs for correct format before passing to the node.
- Check network connectivity and firewall settings if requests fail.
Links and References
- Bedrijfsdata API Documentation (official API docs for detailed endpoint info)
- n8n Documentation (for general usage of custom nodes and credentials)