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 various data retrieval and validation tasks. Specifically, for the Validation & Cleansing resource with the Validate Email Address operation, it validates email addresses using basic validation rules provided by the API.
This node is beneficial when you need to verify the format and validity of email addresses within your workflows, such as before sending marketing emails, registering users, or cleaning contact lists.
Practical example:
You have a list of customer emails collected from a form. Before adding them to your CRM or mailing system, you use this node to validate each email address to reduce bounce rates and improve deliverability.
Properties
| Name | Meaning |
|---|---|
| Email Address | (Required) Enter the email address to validate. |
The "Email Address" property accepts a string input representing the email to be validated.
Output
The node outputs JSON data containing the validation result from the Bedrijfsdata API. The structure typically includes fields indicating whether the email is valid, possibly with additional metadata about the validation status or errors if any.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Bedrijfsdata API.
- The node makes HTTP GET requests to the endpoint
/emailon the base URLhttps://api.bedrijfsdata.nl/v1.2. - Proper configuration of the API key credential in n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an improperly formatted email may result in validation failure or error responses.
- Network connectivity issues can prevent the node from reaching the API.
Error messages:
- Errors related to API request failures will include messages like "Failed to fetch cities" or "Unexpected API response," which indicate problems with the API call or response format.
- Authentication errors will typically mention invalid credentials or unauthorized access.
Resolutions:
- Ensure the API key credential is correctly set up and active.
- Validate the email format before passing it to the node to avoid unnecessary API calls.
- Check network connectivity and proxy settings if applicable.
Links and References
- Bedrijfsdata API Documentation (general reference for API endpoints and usage)
- Email Validation Concepts (background on email address syntax and validation)