> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/capsule-crm/faq.md).

# FAQ

<details>

<summary>Where do I find my Capsule CRM API key?</summary>

In Capsule CRM, click your profile avatar in the top-right corner and go to **My Preferences**. Under the **API Authentication Tokens** section, you can generate a new token. Copy it and paste it into the API key field in Coupler.io when setting up your data flow.

</details>

<details>

<summary>Can I pull data from multiple Capsule CRM accounts into one destination?</summary>

Yes. Create a separate source connection for each Capsule CRM account within the same data flow, then use the **Append** transformation to stack the data into a single table. This is useful if your organization manages multiple Capsule accounts for different regions or brands.

</details>

<details>

<summary>Which entities should I use to build a sales pipeline report?</summary>

Start with **Opportunities**, **Pipelines**, and **Stages**. Use a Join transformation to connect them — Opportunities carry the deal data, Pipelines provide the pipeline name, and Stages give you readable stage labels. Add **Lost reasons** if you want to analyze why deals didn't close.

</details>

<details>

<summary>Why do I see only IDs in the lost reason column instead of reason names?</summary>

The Opportunities entity stores a `lostReasonId` reference, not the label text. Pull in the **Lost reasons** entity as an additional source and use a Join transformation to replace the ID with the corresponding reason name.

</details>

<details>

<summary>Does Coupler.io sync Capsule CRM custom fields?</summary>

Yes, but custom fields are a separate entity — they won't automatically appear inside your Party or Opportunity rows. Add **Custom fields** as a second source in your data flow and join records by ID to enrich your main tables.

</details>

<details>

<summary>Can I send Capsule CRM data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your Capsule CRM data — contacts, deals, tasks — directly to these tools for analysis, summarization, or generating insights from your CRM data.

</details>

<details>

<summary>What does the start date parameter control?</summary>

The start date limits how far back in time Coupler.io pulls records from Capsule CRM. Use the date picker when configuring your data flow to set the earliest date you want data from. Records created before this date won't be included in the sync.

</details>

<details>

<summary>How do I separate person contacts from organization contacts in my export?</summary>

The **Parties** entity includes a `type` field that indicates whether a record is a `person` or an `organization`. Filter or group by this field in your destination to work with each type separately.

</details>

{% hint style="info" %}
For a full list of available fields per entity, see [Data Overview](/sources/category/crm/capsule-crm/data-overview.md). If your sync isn't behaving as expected, check [Common Issues](/sources/category/crm/capsule-crm/common-issues.md) for troubleshooting steps. For setup recommendations specific to Capsule CRM, visit [Best Practices](/sources/category/crm/capsule-crm/best-practices.md).
{% 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 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.coupler.io/sources/category/crm/capsule-crm/faq.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.