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

# Data and integrations

Connect your CRM, manage lead fields, and enrich prospects.

Connect the tools that supply lead data and receive workflow actions.

Start with your CRM and calendars. Add enrichment, messaging, sequencing, and AI connections as your workflow needs them.

## Choose a guide

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>CRM and identities</strong></td><td>Connect records and map the right owners.</td><td><a href="/data-and-integrations/crm.md">CRM connections and identities</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FLETsWfDJ31mnh0s5ihux%2Fdistro3-crm.webp?alt=media">distro3-crm.webp</a></td></tr><tr><td><strong>Field catalog</strong></td><td>Define reusable person and company fields.</td><td><a href="/data-and-integrations/field-catalog.md">Field catalog</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FUaHC1oqCqELJxBXi0BCe%2Fdistro3-fields.webp?alt=media">distro3-fields.webp</a></td></tr><tr><td><strong>Enrichment and chains</strong></td><td>Choose providers and understand lookup behavior.</td><td><a href="/data-and-integrations/enrichment.md">Enrichment and chains</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FE6qOvOsL4zqXhFQQar2u%2Fdistro3-enrichment.webp?alt=media">distro3-enrichment.webp</a></td></tr><tr><td><strong>AI and web research</strong></td><td>Use prompts and structured research in a workflow.</td><td><a href="/data-and-integrations/ai.md">AI and web research</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2Fg6FRzkkBbdvBnwpxC65g%2Fdistro3-ai.webp?alt=media">distro3-ai.webp</a></td></tr></tbody></table>

A connected account is one prerequisite. The selected operation must also have the required permissions, sender or host, and resource access.

Use simulation for path checks and controlled provider tests for acceptance. Review the external step's delivery details when the result is uncertain.

Check [Integration availability](/data-and-integrations/availability.md) before publishing a provider action.

## More guides

* [Provider support by enrichment surface](/data-and-integrations/provider-support.md)
* [Pre-submit enrichment](/data-and-integrations/pre-submit.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 dynamically by asking a question.

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

```
GET https://docs.distro.so/data-and-integrations.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 `build a script that syncs our docs to a CMS` 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.