> For the complete documentation index, see [llms.txt](https://docs.patagon.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patagon.ai/en/troubleshooting/crm-integration.md).

# How to connect your CRM via ApiDeck

Patagon AI connects to CRMs through ApiDeck, a unified API integration layer. Supported CRMs include HubSpot, Salesforce, and Pipedrive.

1. In the sidebar, go to **Agent > Channels & Integrations** and click the **Integrations** tab.
2. Find your CRM in the list and click **Connect**.
3. You'll be redirected to ApiDeck's authorization flow. Log in with your CRM credentials and authorize the connection.
4. Once configured and enabled, CRM sync happens automatically as the agent processes conversations.

## What gets synced

Patagon AI sends standard identity fields and attributes that you have mapped to CRM fields. The exact payload depends on your mappings and connection configuration.

See [How lead fields sync to your CRM](/en/troubleshooting/crm-integration/crm-lead-field-sync.md) for details about timing, field mappings, create and update behavior, and missing fields.

## Troubleshooting sync issues

If leads are not appearing in your CRM after connection:

1. Check the integration status in **Agent > Channels & Integrations > Integrations**. A red status means the connection needs to be re-authorized.
2. Confirm your CRM API credentials haven't expired.
3. Check that your CRM user has the permissions required to create contacts.

For persistent sync issues, contact <support@patagon.ai> with your CRM name and a sample lead that didn't sync.


---

# 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.patagon.ai/en/troubleshooting/crm-integration.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.