> 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/common-issues.md).
# Common Issues
## Connection issues
Authorization fails after entering the API key
Double-check that you copied the full API token from Capsule CRM without any trailing spaces. Tokens are found under **My Preferences → API Authentication Tokens**. If the token still doesn't work, try regenerating a new one and pasting it fresh.
The data flow returns no data after a successful connection
Check the **start date** setting in your data flow configuration. If the start date is set too far in the future, or if no records exist within the selected date range, the sync will return empty results. Use the date picker to set an earlier start date and re-run the flow.
## Missing data
Custom fields are not appearing in my destination
Custom fields are exported as a separate **Custom fields** entity in Coupler.io — they are not automatically merged into Parties or Opportunities. Add the Custom fields entity as an additional source in your data flow and use a Join transformation to connect records by their ID.
Some opportunities or parties are missing from the export
This is usually caused by the start date filter. If a record was created before the configured start date, it may not be included. Try setting your start date further back using the date picker. Also check whether the missing records have been archived or deleted in Capsule CRM — archived records may not appear in API results.
Lost reasons are not showing text — only IDs appear
The Opportunities entity stores `lostReasonId` as a reference ID, not the label text. To see reason names, add the **Lost reasons** entity as a second source in your data flow and use a Join transformation to match IDs to names.
## Permission errors
API key works but certain entities return a permission error
Some Capsule CRM plan tiers restrict access to certain features. If your account doesn't have access to Projects or Boards (for example), those entities will return errors. Check that your Capsule CRM subscription includes the features you're trying to export.
## Data discrepancies
Opportunity values in Coupler.io don't match what I see in Capsule CRM
Capsule CRM stores opportunity values with a currency code. If your account uses multiple currencies, totals in your destination may not be converted — each row will carry its original currency. Aggregate values by currency first, or handle conversion in your destination tool.
Contact records show duplicate entries
Capsule CRM allows the same person to exist as both a Person and an Organization party type, or the same contact may have been added more than once. Use the `type` field to separate people from organizations, and check for duplicate entries by matching on email address.
## Rate limits
The sync fails midway with a rate limit error
Capsule CRM's API enforces rate limits on requests. If you're syncing many large entities simultaneously, you may hit this ceiling. Try splitting your data flow into separate flows per entity, or reduce the number of entities running in a single 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.coupler.io/sources/category/crm/capsule-crm/common-issues.md?ask=&goal=
```
`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.