NeverBounce Email Verification
Overview
This node verifies email addresses using the NeverBounce API and enriches each input item with detailed verification hints. It is useful for workflows that require validating email lists to improve data quality, reduce bounce rates, or ensure accurate contact information before sending emails.
Typical use cases include:
- Cleaning up marketing or sales email lists by verifying addresses.
- Enriching customer records with verification status and suggestions.
- Automating email validation in onboarding or registration processes.
For example, you can input a list of contacts with email fields, and the node will append verification results such as validity status, flags indicating potential issues, and suggested corrections if available.
Properties
| Name | Meaning |
|---|---|
| Email Field | The name of the field in the input data that contains the email address to verify. |
| Additional Fields | A collection of optional settings: - Output Field Name: The field name where the verification results will be stored (default: verification_result). - Timeout: Timeout in seconds for the API request (default: 30). |
Output
The node outputs an array of items where each item's JSON data is enriched with:
A new field (name configurable via "Output Field Name") containing:
valid: Boolean indicating if the email is valid (trueif verified as valid).status: The verification result status string from the API.status_code: Numeric status code from the API response.flags: An array of flags describing any issues or warnings related to the email.suggested_correction: A suggested corrected email address if applicable, ornull.raw_response: The full raw response object from the NeverBounce API.agent_instructions: Additional instructions or hints related to the verification.
email_verified: A boolean flag set totrueindicating the email was processed.verification_timestamp: ISO timestamp string marking when the verification occurred.
If the node encounters errors and "Continue On Fail" is enabled, it outputs error details per failed item instead of stopping execution.
Dependencies
- Requires an API key credential for the NeverBounce service.
- Makes HTTP GET requests to the NeverBounce API endpoint:
https://api.neverbounce.com/v4/single/check. - The node expects the API key to be configured securely within n8n credentials.
Troubleshooting
- No email found in field: Occurs if the specified email field is missing or empty in an input item. Ensure the correct field name is provided and that all items contain this field.
- Invalid email format: Triggered when the email does not match a standard email regex pattern. Verify the input data contains properly formatted email addresses.
- API request failures: Could be due to invalid API keys, network issues, or exceeding rate limits. Check API key validity and network connectivity.
- If "Continue On Fail" is disabled, the node stops on the first error; enabling it allows processing remaining items despite individual failures.