Overview
This node integrates with the VerificarEmails.com API to validate and verify various types of personal and contact information. It supports multiple verification services including email validation, phone number validation (with different methods), postal address validation, and name-related validations such as gender detection, correction, and autocomplete.
Common scenarios where this node is beneficial include:
- Cleaning and verifying customer contact data before importing into CRM systems.
- Validating user input in forms or workflows to reduce errors and improve data quality.
- Enriching datasets with additional insights like gender or country based on names.
- Standardizing postal addresses for shipping or mailing purposes.
Practical examples:
- Validate a list of email addresses to filter out invalid or disposable emails.
- Check phone numbers using HLR lookup to confirm if they are active and reachable.
- Correct misspelled first names or surnames in a database.
- Autocomplete partial names to assist in data entry or search functionalities.
Properties
| Name | Meaning |
|---|---|
| Service | Select which verification service to use. Options: Email validation, Phone validation - HLR Lookup, Phone validation - MNP, Phone validation - Syntactic, Postal Address validation, Name/Surname/Gender validation, Name/Surname correction, Name/surname autocomplete. |
| The email address to validate (shown when "Email validation" service is selected). | |
| Phone | Phone number to validate, depending on the chosen phone validation service: - HLR Lookup: international format, no spaces. - MNP: international format, no spaces, no leading 0 or +. - Syntactic: international format, no spaces, no leading 0 or +. |
| Name | Name or surname to validate for country, gender, and popularity insights (shown when "Name/Surname/Gender validation" service is selected). |
| Address | Postal address to validate and correct to a standardized format (shown when "Postal Address validation" service is selected). |
| Name (Input) | Name or surname to process for correction or autocomplete (required for "Name/Surname correction" and "Name/surname autocomplete" services). |
| Type | Specify whether the input name is a first name (value 1) or a surname (value 0) (required for name correction/autocomplete). |
| Gender | Optional gender hint for name correction/autocomplete: Male (M), Female (F), or unspecified. |
| Country | Optional country code (Alpha-2) to refine name correction/autocomplete results (e.g., US for United States). |
Output
The node outputs an array of JSON objects, each containing:
service: The verification service used (e.g., "email", "phone_hlr").term: The input value that was verified (string or object depending on service).status: The status of the verification result, typically indicating success or failure.apiResponse: The full raw response from the VerificarEmails.com API, containing detailed verification data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the VerificarEmails.com service.
- The node makes HTTP GET requests to the VerificarEmails.com API endpoints.
- Proper configuration of the API key credential in n8n is necessary for operation.
Troubleshooting
- Invalid API Key or Authentication Errors: Ensure the API key credential is correctly configured and valid.
- Incorrect Input Format: Phone numbers must be in the specified international formats without spaces or symbols as described in the property descriptions.
- Missing Required Parameters: For name correction and autocomplete services, the name input and type (first name or surname) are required.
- API Rate Limits or Quotas: If many requests are made in a short time, the API may throttle or reject calls; check your API plan limits.
- Unexpected API Responses: Inspect the
apiResponsefield in the output for error messages or details returned by the API.
Links and References
- VerificarEmails.com API Documentation (for detailed API usage and parameters)
- n8n Documentation on Creating Custom Nodes