# Fluent

Have you ever wondered **how to prevent poor leads** from appearing in your CRM generated by Fluent Forms? **Fluent forms typically don't catch incorrect email addresses** like disposable, gibberish, spam-trap, role/group addresses, typos, which results in low-quality leads.

Upgrade the quality of leads by identifying and removing such invalid leads at the time of capture on Fluent Forms by integrating with Clearout Email Validator.

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

## Steps to integrate Fluent Forms with Clearout WordPress plugin <a href="#kedpr" id="kedpr"></a>

{% stepper %}
{% step %}
**Log in** to your Clearout account, navigate to the ‘**Developer**’ section. Click on '**+Create API Token**,' add a name and description, then click **Create**.

<div data-with-frame="true"><figure><img src="https://93738666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEXQQW0hsXyH0YD4ePoxb%2Fuploads%2FFFG7qALkaa5uP1fbxilK%2FClearout-API-Token-creation.png?alt=media&#x26;token=b973bfc9-5ab1-4d09-a119-91a6fe291c34" alt="Clearout API Token Creation for Fluent Form Integration"><figcaption></figcaption></figure></div>

You’ll see the API token. **Copy Clearout API Token**, then go back to your WordPress site.

<div data-with-frame="true"><figure><img src="https://93738666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEXQQW0hsXyH0YD4ePoxb%2Fuploads%2FwPKUCZDUIqwnHkq3Jga3%2FClearout-API-Token-Fluent%20forms-copying.png?alt=media&#x26;token=5b105b2f-fa88-42fe-955e-da7546e489d1" alt="Copy Clearout API Token Creation for Fluent Form Integration"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}
Set up the Clearout Email Validator plugin. Go to your form **Settings** > **Clearout Email Validator** *(make sure you’ve activated the plugin)*, **paste** your Clearout API token.

Note: By default, the plugin will block role-based addresses and disposable addresses. You can allow either or both by choosing the checkboxes in the settings.&#x20;

You can also enable "**Accept only Business Address as valid**", which will override all the other settings.

<div data-with-frame="true"><figure><img src="https://93738666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEXQQW0hsXyH0YD4ePoxb%2Fuploads%2FGri5NTLQoILzwNM7lOqu%2Fimage1.png?alt=media&#x26;token=6d2bcdcd-0a08-4d44-a42d-6922d2f79a3a" alt="WordPress settings of Clearout Email Validator Plugin"><figcaption></figcaption></figure></div>

Navigate down to '**Apply Validation**' > Select **Fluent Form** > Click on **Apply** to activate the validation.

<div data-with-frame="true"><figure><img src="https://93738666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEXQQW0hsXyH0YD4ePoxb%2Fuploads%2FGlrmWezI6d68X6OYd2M1%2Fimage6-1024x504.png?alt=media&#x26;token=b3e2dbec-4050-484f-88ee-6c2745b19d5a" alt="WordPress settings of Clearout Email Validator Plugin for Fluent Forms"><figcaption></figcaption></figure></div>

That's it!&#x20;

Shown below is **an example** of a Fluent Form integrated with Clearout, identifying an invalid email address in real-time

<div data-with-frame="true"><figure><img src="https://93738666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEXQQW0hsXyH0YD4ePoxb%2Fuploads%2F4FSunqS09F2ZVRvAHVFv%2Fimage5.png?alt=media&#x26;token=05b432cc-7bbb-478e-b4b0-aca7f805a739" alt="Email validation example on Fluent Forms"><figcaption></figcaption></figure></div>

{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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:

```
GET https://docs.clearout.io/integrations/forms/fluent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.