Overview
The Byteplant Email Validator node validates email addresses by querying the Byteplant Email Validator API. It checks if an email address is valid, provides detailed validation information, and categorizes the email status. This node is useful in scenarios where you need to verify user emails before processing them further, such as during user registration, newsletter subscriptions, or data cleansing tasks.
For example, you can use this node to:
- Confirm that a user's email address is deliverable before sending marketing emails.
- Filter out invalid or disposable email addresses from your contact lists.
- Automate email validation workflows to improve data quality.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address to validate. Must be provided for each execution. |
| Timeout | Timeout in seconds for the API request. Default is 10 seconds; minimum 5 seconds, maximum 300 seconds. |
Output
The node outputs JSON data with the following structure:
status(number): Status code returned by the Byteplant API indicating the validation result.info(string): A brief description or message related to the validation status.details(object): Additional detailed information about the email validation.freemail(boolean): Indicates whether the email is from a free email provider.category(string | undefined): A category label corresponding to the status code, derived from predefined status codes.
If the node encounters an invalid or depleted API key, it throws an error indicating this issue.
Dependencies
- Requires an API key credential for the Byteplant Email Validator API.
- Makes HTTP GET requests to
https://api.email-validator.net/api/verify. - The node expects the API key to be configured in n8n credentials under a generic API authentication token.
Troubleshooting
- API Key Invalid or Depleted: If the API key is invalid or has no remaining quota, the node throws an explicit error. To resolve, verify your API key validity and quota on the Byteplant service dashboard.
- Timeout Issues: Setting the timeout too low (below 5 seconds) may cause premature request failures. Ensure the timeout is within the allowed range (5-300 seconds).
- Network Errors: Network connectivity issues or incorrect API endpoint configuration can cause request failures. Verify network access and API URL correctness.
- Error Handling: If "Continue On Fail" is enabled, the node will output the original input along with the error details instead of stopping execution.