QuickEmailVerification

Verify email addresses using QuickEmailVerification API

Overview

This node verifies the validity and quality of email addresses using the QuickEmailVerification API. It is useful for scenarios where you need to validate user emails before processing them further, such as in sign-up forms, marketing campaigns, or data cleansing workflows. The node checks if an email is valid, disposable, role-based, or safe to send to, and provides detailed reasons for invalidity or temporary blocks.

A practical example: Before adding a new subscriber to your mailing list, use this node to verify their email address to reduce bounce rates and improve deliverability.

Properties

Name	Meaning
Email	The email address to verify. Example: `[email protected]`.
Enable Greylisting Retries	Whether to retry verification if the email is temporarily blocked due to greylisting (temporary block).
Retry Delay	Delay in seconds before retrying verification for greylisted emails.
Maximum Retries	Maximum number of retries allowed for greylisted emails.

Output

The node outputs an array of JSON objects, each representing the verification result for one email. Each output JSON contains:

result: Verification status such as valid, invalid, or unknown.
reason: Explanation like accepted_email, invalid_email, temporarily_blocked, etc.
disposable: Boolean indicating if the email domain is disposable.
accept_all: Boolean indicating if the domain accepts all emails.
role: Boolean indicating if the email is role-based (e.g., admin@, info@).
safe_to_send: Boolean indicating if it is safe to send emails to this address.
email: Normalized email address.
source: Origin of the result (api, addressCache, or domainCache).
verifiedAt: Timestamp when the verification was performed.
remainingCredits: Number of remaining API credits.
retryInfo (optional): Details about any retries performed due to greylisting, including whether retries were done, count, and success.

No binary data output is produced by this node.

Dependencies

Requires an API key credential for the QuickEmailVerification service.
Uses local file caching for address and domain results to optimize repeated lookups.
Caching directories are created under the user's home directory in .n8n/quickemailverification-address-cache and .n8n/quickemailverification-domain-cache.
Node dependencies include keyv and keyv-file for caching, and a custom QuickEmailVerification API client.

Troubleshooting

Temporary Block / Greylisting: If the email verification returns temporarily_blocked, enabling greylisting retries with appropriate delay and max retries can help get a definitive result.
Cache Issues: Corrupted cache files may cause errors; the node automatically cleans up cache files if detected but manual cleanup might be needed if errors persist.
API Key Errors: Invalid or missing API keys will prevent verification. Ensure the API key credential is correctly configured.
Rate Limits: Exceeding API credit limits will cause failures; monitor remainingCredits in output to avoid this.
Network Issues: Connectivity problems to the QuickEmailVerification API will cause errors; check network access and proxy settings if applicable.