> 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/data-pulse/supported-data-sources.md).

# Supported Data Sources

Data Pulse connects to the systems where your contacts live and keeps that data clean automatically. This page explains what a data source is, what Data Pulse does with one once it is connected, and which sources are supported today.

{% hint style="info" %}
New to Data Pulse? Start with the [Overview](https://docs.clearout.io/data-pulse/overview.md) to understand the pulsing engine, then come back here to connect your first source.
{% endhint %}

### What is a data source?

A data source is any system that stores your contact records and that Data Pulse can connect to, monitor, and write results back into. In most cases this is your CRM (for example, HubSpot or Salesforce).

When you connect a data source, Data Pulse becomes a live data-quality layer on top of it. It does not replace your CRM and it does not move your data out of it. It listens for contacts as they are created and as they are updated, validates them, and returns the results to the same records.

{% hint style="warning" %}
Write-back is append-only. Data Pulse only adds or updates its own Clearout fields on a contact. Your original CRM values are never changed or removed.
{% endhint %}

### Supported sources at a glance

<table><thead><tr><th width="127">Data source</th><th width="97">Status</th><th width="177">Connection method</th><th width="162">What it monitors</th><th>Setup performed by</th></tr></thead><tbody><tr><td><a href="https://docs.clearout.io/integrations/hubspot/hubspot-crm.md#how-data-pulse-works">HubSpot</a></td><td>Live</td><td>OAuth</td><td>Contacts, on creation and update</td><td>Any user with HubSpot install permission</td></tr><tr><td><a href="https://docs.clearout.io/integrations/salesforce.md#how-salesforce-two-way-sync-works">Salesforce</a></td><td>Live</td><td>Managed package plus OAuth-connected app</td><td>Leads and Contacts, on creation and update</td><td>Salesforce administrator (one-time), then any assigned user</td></tr></tbody></table>

{% hint style="info" %}
Want a source that is not listed here? We prioritize the next integration based on customer demand. [Tell us which CRM](https://changelog.clearout.io/?_gl=1*7ajw74*_gcl_au*MjEyMDI0OTQyOC4xNzc4NzU2NTkzLjEzOTA5ODUyODcuMTc4NTE0OTI1NS4xNzg1MTQ5MjU0LjczMjc1MjA4Ni4xNzg1MTI5MDE4LjE3ODUxNDkyNTQ.*_ga*MTY5NTc4NTA3NS4xNzMxOTk3OTQy*_ga_QWRSQT3D41*czE3ODUxMjQwOTMkbzUzMCRnMSR0MTc4NTE1MzYzMSRqNTUkbDAkaDEyMTYzMTU1MTU.) your team runs and we'll move it up the queue.
{% endhint %}

### Fields Data Pulse validates

Across every supported source, Data Pulse currently validates three field types. You choose which ones to enable during setup, and at least one must be selected.

* **Email** - deliverability status, safe-to-send, disposable, role-based, free-domain, and gibberish checks.
* **Phone** - reachability, line type (mobile, fixed, or VoIP), carrier, country, and timezone.&#x20;
* **Name** - normalization plus gibberish and placeholder detection.

For the full list of input and output fields, see Implementation & Setup.

### Fields Data Pulse Updates

After real-time verification, Data Pulse writes its results into [Clearout Standard Fields](https://docs.clearout.io/data-enrichment/clearout-standard-fields.md) on your contact records. These fields hold the validation status and enriched details for the fields you enabled, for example email status, safe-to-send, phone line type, and normalized name. Your existing properties are not touched.

### Next steps

* [Connect HubSpot](https://docs.clearout.io/integrations/hubspot/hubspot-crm.md#how-the-hobspot-two-way-sync-works)
* [Connect Salesforce](https://docs.clearout.io/integrations/salesforce.md#how-salesforce-two-way-sync-works)
* [Review Features & Functionality and FAQs](https://docs.clearout.io/data-pulse/faqs.md)


---

# 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/data-pulse/supported-data-sources.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.
