Overview
This node validates email addresses using the Truelist API. It is designed to check whether an email address is valid and trustworthy by querying the external Truelist service. This can be useful in scenarios such as user registration forms, marketing lists cleaning, or any workflow where verifying the authenticity of an email address is important to reduce bounce rates or fraud.
For example, you might use this node to validate each email address submitted through a form before adding it to your mailing list, ensuring only valid emails are stored and contacted.
Properties
| Name | Meaning |
|---|---|
| The email address to validate. |
Output
The node outputs JSON data containing the response from the Truelist API for each input email address. The structure of the output JSON corresponds directly to the API's verification result, which typically includes details about the validity and status of the email address.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for the Truelist service.
- The node makes HTTP GET requests to the Truelist API endpoint
https://api.truelist.io/api/v1/verify_inline. - The API key must be provided via n8n credentials configuration to authorize requests.
Troubleshooting
- Invalid or missing API key: If the API key is incorrect or not set, the node will fail to authenticate with the Truelist API. Ensure the API key credential is correctly configured.
- Network issues: Connectivity problems may cause request failures. Verify network access to
api.truelist.io. - API rate limits: Excessive requests might be throttled by the Truelist API. Check your API plan limits.
- Malformed email input: Providing an empty or improperly formatted email string may lead to unexpected API responses or errors. Always ensure the "Email" property is correctly set.
Links and References
- Truelist API Documentation (for detailed API response structure and usage)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n)