> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/integrations/hubspot.md).

# HubSpot 

Sync verified contacts into HubSpot ecosystems

The **HubSpot integration** lets you use Clearout’s verification and enrichment capabilities directly inside your HubSpot [CRM](/integrations/hubspot/hubspot-crm.md), [forms](/integrations/hubspot/hubspot-forms.md), [chatflows](/integrations/hubspot/hubspot-chatflows.md), and [workflows](/integrations/hubspot/hubspot-workflows.md). It helps you keep contacts clean, block fake signups at the source, and ensure sales and marketing always work with accurate, reachable data.​

**With Clearout connected to HubSpot**, you can:

* Validate and clean existing contacts in HubSpot CRM before campaigns go out.
* Validate emails in real time on HubSpot forms and chatflows to stop invalid or disposable addresses.
* Use HubSpot workflows to automatically verify, score, and segment contacts as they are created or updated.​

{% hint style="success" %}
Data Pulse verifies contacts in your HubSpot CRM in real time, both when they are created and when their name, email, or phone is updated. It works with free HubSpot accounts. Once [set up](/data-pulse/implementation-and-setup.md), no further action is needed - each new contact's email, phone, and name are verified automatically.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clearout.io/integrations/hubspot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.