> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/relate/email/email-marketing-how-to-configure-validemail-and-use-email-verification-in-sprinthub.md).

# Email Marketing - How to configure ValidEmail and use email verification in SprintHub

The integration with **ValidEmail** allows you to validate email addresses before sending campaigns, registrations, or automations in SprintHub. This reduces bounces, improves deliverability, and keeps your database clean.

***

{% embed url="<https://www.youtube.com/watch?v=4q36MXCbcjU>" %}

***

### ✔️ Bulk verification via Contacts

In addition to individual verification, you can validate emails in bulk using SprintHub filters.

1. Access **System Settings > General > Contacts**.
2. Use the filter **“Does the contact have an email?”** and select the option:
   * **Yes, and the email exists**
3. Integrate with ValidEmail through the link shown on the dashboard.
   * Use the code **SPRINTHUB20** to activate the benefit.
   * Enter your **API Key** to connect the service.

{% embed url="<https://validemail.net/?aff=SPRINTHUB>" %}

SprintHub will automatically send all filtered emails for validation in ValidEmail.

The process runs in the background and you can track its progress on the dashboard.

***

### ✔️ Automation with email verification

SprintHub also allows you to automate email verification within automation flows.

#### **How to configure it within the flow**

1. Access **Automation Flow**, **CRM Automation**, **SAC 360º** or **Chatbot**.
2. Create a new flow or edit an existing one.
3. Add the condition **“Does the contact have an email?”** and select:
   * **Yes, and the email exists**
4. Integrate with ValidEmail through the link shown on the dashboard.
   * Use the code **SPRINTHUB20** to activate the benefit.
   * Enter your **API Key** to connect the service.

{% embed url="<https://validemail.net/?aff=SPRINTHUB>" %}

***

### ✔️ Define the flow behavior according to the validation status

After verification, configure the actions the flow should perform according to the result:

* **Continue the flow** only if the email is **Valid**
* **End the flow** immediately for emails **Invalid**
* **Add tag** to the contact (e.g.: *invalid email*)
* **Notify an operator** automatically, if necessary

This logic helps keep your database updated, improves sending quality, and avoids wasting automated actions.

***

### 📊 Where to view the verification result

The results are visible in the following places:

* **Contact record**
* **Contacts list** (column *Email status*)
* **Contact history**
* **Reports**, when enabled

***

### 📝 Important notes

* Each verification consumes credits from your ValidEmail account.
* If the **API Key expires** or reaches the **usage limit**, verifications will be paused.
* ValidEmail **does not send**, only validates addresses.
* We recommend validating emails before campaigns to reduce SMTP rejections and improve deliverability.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/relate/email/email-marketing-how-to-configure-validemail-and-use-email-verification-in-sprinthub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.