Verifi Email icon

Verifi Email

Email validation and domain health check using VerifiEmail API

Actions2

Overview

This node integrates with the VerifiEmail API to perform two main functions: validating individual email addresses and checking the health and configuration of a domain. The "Check Domain Health" operation specifically assesses the domain's email-related settings, such as DKIM selectors, to ensure proper email authentication and deliverability.

Common scenarios for using this node include:

  • Verifying that a domain is correctly configured for sending authenticated emails.
  • Diagnosing issues related to email delivery failures by inspecting domain health.
  • Automating domain health checks as part of an email infrastructure monitoring workflow.

For example, a marketing team could use this node to regularly verify their sending domains' configurations to maintain high email deliverability rates.

Properties

Name Meaning
Domain The domain name to check for health and configuration issues (e.g., "example.org").
Selector Optional DKIM selector to check within the domain's DNS records. Common values: "google", "default".

Output

The output JSON object contains the following fields:

  • domain: The domain that was checked.
  • selector: The DKIM selector used in the check, or null if none was specified.
  • Additional fields returned by the VerifiEmail API representing the domain's health status and configuration details.

The exact structure depends on the API response but generally includes information about DNS records, DKIM validity, SPF records, and other email authentication mechanisms.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the VerifiEmail service.
  • Makes HTTP GET requests to the VerifiEmail API endpoints:
    • https://api.verifi.email/v1/domain/check for domain health checks.
  • The node expects the API key to be provided via n8n credentials configured for this node.

Troubleshooting

  • Missing Domain: If the "Domain" property is empty or invalid, the node will throw an error indicating that the domain is required.
  • Invalid API Key or Authentication Failure: Errors from the API due to invalid or missing credentials will cause the node to fail unless "Continue On Fail" is enabled.
  • Network Issues: Connectivity problems to the VerifiEmail API endpoint may result in request timeouts or errors.
  • Incorrect Selector: Using an unsupported or incorrect DKIM selector might lead to incomplete or failed checks.

To resolve these issues:

  • Ensure the domain name is correctly entered.
  • Verify that the API key credential is valid and has necessary permissions.
  • Check network connectivity and firewall settings.
  • Use common selectors like "google" or "default" unless a custom selector is known.

Links and References

Discussion