> 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/close-com/faq.md).

# FAQ

<details>

<summary>Which Close.com plan do I need to use the API?</summary>

API access is available on Close.com paid plans. Free trials may have limited or no API access. Check your plan details in Close.com under **Settings → API Keys** — if you can generate a key, you have API access.

</details>

<details>

<summary>Where do I find my Close.com API key?</summary>

In Close.com, click your profile icon, go to **Settings → API Keys**, and generate a new key. Copy it immediately — Close.com won't show the full key again after you leave that page.

</details>

<details>

<summary>Can I connect multiple Close.com organizations to Coupler.io?</summary>

Yes. Each API key is scoped to one Close.com organization. If you manage multiple orgs, create a separate data flow for each one using the corresponding org's API key. You can then use the Append transformation to combine data from multiple orgs into a single destination.

</details>

<details>

<summary>How do I get rep names instead of user IDs in my reports?</summary>

Add the **Users** entity as an additional source in your data flow, then use the Join transformation to match the `user_id` (or `assigned_to`) field on your activity or lead entity with the `id` field on Users. This will resolve IDs to names and email addresses.

</details>

<details>

<summary>Can I pull data from a specific date range only?</summary>

Yes. When configuring your source in Coupler.io, use the date picker in the **Start date** field to set the earliest date for data retrieval. Leave it blank to pull all available historical data.

</details>

<details>

<summary>Why does the Events entity take so long to sync?</summary>

The Events entity logs every action across your Close.com account and can be extremely large for active teams. Set a start date to limit the volume, and consider routing this entity to BigQuery rather than Google Sheets for better performance.

</details>

<details>

<summary>Can I use Close.com data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your leads, opportunities, or call activity data directly to these tools for analysis, summarization, or forecasting.

</details>

<details>

<summary>What's the best way to build a pipeline report?</summary>

Start with the **Opportunities** entity and join it with **Pipelines** (on `pipeline_id`) and **Users** (on `user_id`). Use Coupler.io's Aggregate transformation to group by pipeline stage and sum the `value` field (remember to divide by 100). Send the result to Looker Studio or Google Sheets for visualization.

</details>

<details>

<summary>Why are my custom field columns showing IDs instead of field names?</summary>

Close.com uses internal IDs for custom field column headers. Pull the matching custom fields definition entity (e.g., Lead custom fields) and join it to your main entity on the field ID to get human-readable names. See the Data Overview for more detail.

</details>

{% hint style="info" %}
For a full list of available fields per entity, see the [Data Overview](/sources/category/crm/close-com/data-overview.md). For help with sync errors or missing records, visit [Common Issues](/sources/category/crm/close-com/common-issues.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/close-com/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.