Verifi Email icon

Verifi Email

Email validation and domain health check using VerifiEmail API

Actions2

Overview

The node integrates with the VerifiEmail API to perform email validation and domain health checks. It is useful for scenarios where you need to verify the validity of an email address before sending communications or to assess the configuration and reputation of a domain to ensure reliable email delivery.

Practical examples include:

  • Validating user-submitted email addresses during sign-up to reduce bounce rates.
  • Checking the health and configuration of your sending domains to improve email deliverability.
  • Automating email hygiene processes in marketing workflows.

Properties

Name Meaning
Email The email address to validate. This should be a single email string, e.g., user@example.org.

Output

The output JSON object contains the original email address plus the response data from the VerifiEmail API's validation endpoint. This typically includes detailed information about the email's validity, such as whether it is syntactically correct, if the mailbox exists, and other verification results provided by the API.

Example output structure (simplified):

{
  "email": "support@verifi.email",
  "is_valid": true,
  "reason": "Accepted email",
  "details": {
    // Additional validation details from the API
  }
}

No binary data is output by this node.

Dependencies

  • Requires an API key credential for the VerifiEmail service.
  • The node makes HTTP GET requests to the VerifiEmail API endpoints.
  • Network access to https://api.verifi.email must be available.
  • Properly configured credentials must be set up in n8n to authenticate API requests.

Troubleshooting

  • Missing Email Address: If the email property is empty or missing, the node will throw an error indicating that the email address is required.
  • Invalid API Key or Authentication Failure: Errors related to authentication usually mean the API key credential is incorrect or missing.
  • API Request Failures: Network issues or API downtime can cause request failures; check connectivity and API status.
  • Continue On Fail Behavior: If enabled, the node will output error messages per item instead of stopping execution on failure.

Links and References

Discussion