Actions2
Overview
This node integrates with the EmailVerify.io API to perform email-related operations. Specifically, it can verify the validity of an email address, find an email address based on a person's name and domain, or check the account balance for the API usage.
A common use case is validating user-provided email addresses in sign-up forms to reduce bounce rates and improve deliverability. Another scenario is discovering professional email addresses when only a name and company domain are known, useful for sales or recruitment outreach. Checking the account balance helps monitor API usage limits.
For the Verify Email operation, the node sends the provided email address to the API and returns detailed verification results indicating whether the email is valid, risky, or invalid.
Properties
| Name | Meaning |
|---|---|
The email address you want to verify. Example: name@email.com |
Output
The node outputs JSON data containing the response from the EmailVerify.io API for the verification request. This typically includes fields such as:
- Whether the email is valid or not.
- Risk assessment or confidence score.
- Additional metadata about the email status (e.g., syntax correctness, domain validation, mailbox existence).
The output is structured as an array of JSON objects, each corresponding to an input item processed by the node.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for EmailVerify.io to authenticate requests.
- The node makes HTTP GET requests to EmailVerify.io endpoints (
/validatefor verification). - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication errors.
- Providing malformed or empty email addresses may result in API errors or invalid responses.
- Network connectivity problems can lead to request timeouts or failures.
Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, rate limit exceeded, or invalid parameters.
Resolution tips:
- Ensure the API key credential is correctly set up and active.
- Validate email inputs before running the node.
- Check network access and firewall settings allowing outbound HTTPS requests.