Neverbounce icon

Neverbounce

Verify email addresses using Neverbounce API
Join our community

Overview

This node integrates with the Neverbounce API to verify the validity of email addresses. It is useful in scenarios where you need to ensure that email addresses are deliverable and reduce bounce rates, such as cleaning mailing lists, validating user input during sign-up, or verifying contact information before sending marketing campaigns.

For example, you can input an email address, and the node will return detailed verification results indicating whether the email is valid, invalid, disposable, or catch-all, helping you decide if it should be used for communication.

Properties

Name Meaning
Email The email address to verify. Must be a valid string formatted as an email (e.g., name@email.com).

Output

The node outputs a JSON object containing the response from the Neverbounce API's single email check endpoint. This includes detailed information about the email verification status, such as:

  • Whether the email is valid or invalid.
  • If the email is disposable or a catch-all.
  • Additional metadata provided by Neverbounce regarding the email quality.

The output is structured as an array of JSON objects, each corresponding to an input item processed. There is no binary data output.

Example output snippet (simplified):

[
  {
    "result": "valid",
    "flags": [],
    "address": "name@email.com",
    "disposable": false,
    "catch_all": false,
    "role": false,
    "reason": "Accepted Email"
  }
]

Dependencies

  • Requires an API key credential for the Neverbounce service.
  • The node makes HTTP GET requests to the Neverbounce API endpoint: https://api.neverbounce.com/v4/single/check.
  • The API key must be configured in n8n credentials prior to using this node.

Troubleshooting

  • Common issues:

    • Invalid or missing API key: The node will fail to authenticate with the Neverbounce API.
    • Rate limiting: Excessive requests may lead to throttling by the API.
    • Invalid email format: The API may reject improperly formatted emails.

  • Error messages:

    • Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures or invalid parameter errors.

  • Resolutions:

    • Ensure the API key credential is correctly set up and active.
    • Validate email inputs before running the node.
    • Use "Continue On Fail" option to handle individual item errors gracefully.

Links and References

Discussion