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 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 before processing or storing them, helping reduce errors caused by invalid emails in workflows such as contact management, marketing automation, or user registration systems.
Example use case:
You have a list of customer emails collected from a form and want to ensure they are valid before sending newsletters. This node can validate each email address and filter out invalid ones automatically.
Properties
| Name | Meaning |
|---|---|
| Email Address | (Required) Enter the email address to validate. Example: name@email.com |
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 and possibly additional metadata about the validation status.
Since this node performs only basic validation, the output JSON will primarily confirm if the email address format is correct according to the API's rules.
No binary data output is involved.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Needs an API key credential configured in n8n for authentication with the Bedrijfsdata service.
- The node sends a GET request to the
/emailendpoint of the Bedrijfsdata API with the email address as a query parameter.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Network connectivity problems may prevent reaching the Bedrijfsdata API.
- Providing an empty or malformed email address will result in validation failure or error responses.
Error messages:
- Errors related to API request failures will include messages like "Failed to fetch cities" or "Unexpected API response," which indicate issues with the external API call.
- If the email parameter is missing or empty, the node might throw an error indicating that the required input is not provided.
Resolution tips:
- Ensure the API key credential is correctly set up and has necessary permissions.
- Verify network access to the Bedrijfsdata API endpoint.
- Validate input email addresses before passing them to the node to avoid empty or invalid strings.
Links and References
- Bedrijfsdata API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on Credentials (to configure API keys securely)