> 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.md).

# Close.com

Sync Close.com leads, contacts, opportunities, and sales activities into Google Sheets, BigQuery, or ChatGPT via Coupler.io.

Close.com is a CRM built for sales teams, combining lead management, calling, emailing, and pipeline tracking in one place. Connecting it to Coupler.io lets you pull your sales data into any destination for reporting, analysis, or automation — without manual exports.

**Why connect Close.com to Coupler.io?**

* Sync leads, contacts, opportunities, and all activity types (calls, emails, SMS, meetings) into Google Sheets, BigQuery, Excel, or AI tools like ChatGPT or Looker Studio
* Combine Close.com data with other sources using Join or Append transformations — for example, join opportunities with contacts to build a full sales pipeline view
* Keep your reports automatically up to date on a schedule without touching Close.com
* Use Aggregate transformations to roll up activity counts, pipeline values, or deal stage distributions

## Prerequisites

* A Close.com account with API access (available on all paid plans)
* Your Close.com API key (find it under **Settings → API Keys** in Close.com)
* A Coupler.io account

## Quick start

{% hint style="success" %}
If you want a pipeline report, start with the **Leads**, **Opportunities**, and **Contacts** entities — these three together give you the most complete view of your sales funnel.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** From your Coupler.io dashboard, click **Add data flow** and search for **Close.com** as your source.
{% endstep %}

{% step %}
**Enter your Close.com API key.** In Close.com, go to **Settings → API Keys**, generate a new key if you don't have one, and paste it into Coupler.io. Click **Connect**.
{% endstep %}

{% step %}
**Select the entity you want to sync.** Choose from entities like Leads, Contacts, Opportunities, Call activities, and more. Each entity becomes a separate source within your data flow.
{% endstep %}

{% step %}
**Set a start date (optional).** Use the date picker to limit data to a specific time range, or leave it blank to pull all available data.
{% endstep %}

{% step %}
**Choose your destination.** Select where you want the data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm data is coming through correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                               | What it contains                                    |
| ------------------------------------ | --------------------------------------------------- |
| Leads                                | Company or person records at the top of your funnel |
| Contacts                             | Individual people linked to leads                   |
| Opportunities                        | Deals with value, status, and pipeline stage        |
| Call activities                      | Logged calls with duration and outcome              |
| Email activities                     | Sent and received emails                            |
| SMS activities                       | Text message activity                               |
| Meeting activities                   | Scheduled and completed meetings                    |
| Note activities                      | Manual notes added to leads                         |
| Events                               | All activity events across the account              |
| Pipelines                            | Pipeline definitions and stages                     |
| Lead statuses                        | Status labels for leads                             |
| Opportunity statuses                 | Status labels for opportunities                     |
| Users                                | Team members in your Close.com account              |
| Roles                                | User permission roles                               |
| Lead tasks                           | Open tasks linked to leads                          |
| Missed call tasks                    | Tasks generated from missed calls                   |
| Voicemail tasks                      | Tasks generated from voicemails                     |
| Email sequences                      | Automated email sequence definitions                |
| Email templates                      | Saved email templates                               |
| Smart views                          | Saved filtered views of leads                       |
| Custom activities                    | Custom activity type records                        |
| Lead custom fields                   | Custom field definitions for leads                  |
| Contact custom fields                | Custom field definitions for contacts               |
| Opportunity custom fields            | Custom field definitions for opportunities          |
| Activity custom fields               | Custom field definitions for activities             |
| Integration links                    | Third-party integration references                  |
| Dialers                              | Power dialer session data                           |
| Send as                              | Email send-as account configurations                |
| Google connected accounts            | Linked Google accounts                              |
| Zoom connected accounts              | Linked Zoom accounts                                |
| Custom email connected accounts      | Custom SMTP/IMAP email accounts                     |
| Email bulk actions                   | Bulk email action records                           |
| Sequence subscription bulk actions   | Bulk sequence enrollment actions                    |
| Delete bulk actions                  | Bulk delete action records                          |
| Edit bulk actions                    | Bulk edit action records                            |
| Created activities                   | Activity creation events                            |
| Email thread activities              | Email conversation threads                          |
| Lead status change activities        | Log of lead status changes                          |
| Opportunity status change activities | Log of opportunity status changes                   |
| Task completed activities            | Log of completed tasks                              |
| Incoming email tasks                 | Tasks from inbound emails                           |
| Email followup tasks                 | Follow-up email reminders                           |
| Answered detached call tasks         | Tasks from answered calls without a lead            |
| Incoming SMS tasks                   | Tasks from inbound SMS                              |
| Opportunity due tasks                | Tasks triggered by opportunity due dates            |

## Close.com data overview

Close.com exposes a wide range of CRM data through Coupler.io, covering your full sales workflow — from lead capture and contact management through pipeline tracking, communication activity, and task management.

## Entity reference

| Entity group  | Entities                                                                                                                                 |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Core CRM      | Leads, Contacts, Opportunities                                                                                                           |
| Activities    | Call, Email, SMS, Meeting, Note, Email thread, Created, Lead status change, Opportunity status change, Task completed, Custom activities |
| Tasks         | Lead tasks, Incoming email, Email followup, Missed call, Voicemail, Answered detached call, Opportunity due, Incoming SMS                |
| Configuration | Pipelines, Lead statuses, Opportunity statuses, Email templates, Email sequences, Smart views, Roles, Users, Send as, Dialers            |
| Custom fields | Lead, Contact, Opportunity, Activity custom fields                                                                                       |
| Integrations  | Google connected accounts, Zoom connected accounts, Custom email connected accounts, Integration links                                   |
| Bulk actions  | Email, Sequence subscription, Delete, Edit bulk actions                                                                                  |

## Key fields by entity

#### Leads

| Field         | Description                                      |
| ------------- | ------------------------------------------------ |
| id            | Unique lead identifier                           |
| name          | Lead/company name                                |
| status\_label | Current lead status (e.g., Potential, Qualified) |
| status\_id    | ID of the lead status                            |
| assigned\_to  | User ID of the assigned rep                      |
| date\_created | When the lead was created                        |
| date\_updated | When the lead was last updated                   |
| url           | Website URL                                      |
| addresses     | Physical address data                            |
| custom fields | Any custom fields defined for leads              |

#### Contacts

| Field         | Description                      |
| ------------- | -------------------------------- |
| id            | Unique contact identifier        |
| lead\_id      | The lead this contact belongs to |
| name          | Contact full name                |
| title         | Job title                        |
| emails        | Email addresses                  |
| phones        | Phone numbers                    |
| date\_created | When the contact was created     |

#### Opportunities

| Field           | Description                          |
| --------------- | ------------------------------------ |
| id              | Unique opportunity identifier        |
| lead\_id        | Associated lead                      |
| status\_label   | Current opportunity status           |
| status\_type    | Won, Lost, or Active                 |
| value           | Deal value (in cents)                |
| value\_currency | Currency code                        |
| pipeline\_id    | Pipeline this opportunity belongs to |
| close\_date     | Expected or actual close date        |
| user\_id        | Assigned rep                         |
| date\_created   | When the opportunity was created     |

#### Call activities

| Field          | Description                           |
| -------------- | ------------------------------------- |
| id             | Unique call activity ID               |
| lead\_id       | Associated lead                       |
| user\_id       | Rep who made or received the call     |
| direction      | Inbound or outbound                   |
| duration       | Call duration in seconds              |
| status         | Completed, missed, voicemail, etc.    |
| date\_created  | When the call was logged              |
| recording\_url | Link to call recording (if available) |

#### Email activities

| Field         | Description               |
| ------------- | ------------------------- |
| id            | Unique email activity ID  |
| lead\_id      | Associated lead           |
| direction     | Inbound or outbound       |
| subject       | Email subject line        |
| sender        | Sender email address      |
| status        | Sent, received, draft     |
| date\_created | When the email was logged |

#### Pipelines

| Field    | Description                             |
| -------- | --------------------------------------- |
| id       | Unique pipeline ID                      |
| name     | Pipeline name                           |
| statuses | List of stages/statuses in the pipeline |

## Common field combinations

* **Pipeline performance:** Join Opportunities with Pipelines on `pipeline_id` to see deal values broken down by pipeline and stage
* **Rep activity report:** Join Call activities and Email activities with Users on `user_id` to compare outreach volume per rep
* **Lead funnel:** Join Leads with Lead status change activities to track how leads move through statuses over time
* **Contact-to-deal mapping:** Join Contacts with Opportunities via `lead_id` to connect individual people to active deals
* **Task follow-through:** Append all task entity types (lead tasks, missed call tasks, voicemail tasks, etc.) using the Append transformation to get a unified task list

## Use cases by role

{% tabs %}
{% tab title="Sales managers" %}

* Pull **Opportunities** into Google Sheets or Looker Studio to build a live pipeline dashboard with deal values, close dates, and stages
* Use **Call activities** and **Email activities** to track rep outreach volume and compare activity levels across the team
* Monitor **Lead status change activities** to identify where leads are stalling in your funnel
* Join **Leads** with **Users** to see which rep owns each lead and how long leads have been in each status
  {% endtab %}

{% tab title="Sales reps" %}

* Export your **Lead tasks** and **Missed call tasks** to a spreadsheet to prioritize follow-ups outside Close.com
* Use **Note activities** to review call notes and prep for follow-up conversations
* Track your own **Opportunity** win rates by filtering on your `user_id` and grouping by `status_type`
  {% endtab %}

{% tab title="Revenue ops" %}

* Aggregate **Opportunities** by `pipeline_id` and `status_type` to calculate conversion rates at each stage
* Join **Email sequences** with **Email activities** to measure sequence engagement
* Sync **Custom fields** entities to document your field schema and audit data quality across leads, contacts, and opportunities
* Use the **Events** entity for a full audit trail of account activity
  {% endtab %}

{% tab title="Marketing teams" %}

* Pull **Leads** with `date_created` and `status_label` to measure lead quality and conversion from marketing campaigns
* Join **Contacts** with **Leads** to build enriched contact lists for re-engagement
* Export **Email templates** and **Email sequences** to audit messaging consistency across the team
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Opportunity `value` is stored in **cents** — divide by 100 to get the currency value in your reports
* The **Events** entity captures all activity across the account and can be very large; use a start date to limit the volume
* Custom field values appear on their parent entities (Leads, Contacts, Opportunities) — pull the corresponding custom field definitions entity to get human-readable field names
* Close.com user IDs appear on most entities as `user_id` or `assigned_to` — join with the **Users** entity to resolve these to names
* The **Smart views** entity exports view definitions, not the leads inside those views — use the **Leads** entity with filtering for that

## Close.com common issues

### Connection issues

<details>

<summary>My API key is rejected when connecting</summary>

Double-check that you copied the full API key from Close.com without any leading or trailing spaces. In Close.com, go to **Settings → API Keys** and generate a new key if needed. Also confirm that your Close.com plan includes API access — the API is available on paid plans only.

</details>

<details>

<summary>The data flow fails immediately after connecting</summary>

This often happens if the API key belongs to a user with limited permissions. Try using an API key generated by an admin user. Also check whether your Close.com organization has API rate limits that might be cutting off the initial request.

</details>

### Missing data

<details>

<summary>Some leads or opportunities are missing from my sync</summary>

If you set a start date, only records created or updated after that date will sync. Use the date picker to adjust the range, or clear the start date entirely to pull all available data. Also check whether the missing records belong to a different Close.com organization — each API key is scoped to one org.

</details>

<details>

<summary>Custom field values are blank on lead or contact records</summary>

Custom field values are included in the Leads, Contacts, or Opportunities entity output, but the column names use the internal field ID rather than the display name. Pull the corresponding custom fields entity (e.g., **Lead custom fields**) to get a mapping between field IDs and their labels, then use a Join transformation to resolve the names.

</details>

<details>

<summary>The Events entity returns no data</summary>

The Events entity can return a very large dataset. If you didn't set a start date, the sync may be timing out before it completes. Use the date picker to set a recent start date and reduce the volume of records being pulled.

</details>

### Permission errors

<details>

<summary>I'm getting a 403 or "unauthorized" error on certain entities</summary>

Some entities — particularly bulk action logs and admin-level configuration entities — may require admin-level API access. If your API key belongs to a standard user, try regenerating the key as an admin user in Close.com under **Settings → API Keys**.

</details>

### Data discrepancies

<details>

<summary>Opportunity values in Coupler.io don't match what I see in Close.com</summary>

Close.com stores opportunity values in **cents** (e.g., $1,500 = 150000). Divide the `value` field by 100 in your destination to get the correct currency amount. You can do this directly in a Google Sheets formula or as a calculated field in Looker Studio.

</details>

<details>

<summary>User names are showing as IDs instead of names</summary>

Most activity and lead entities store the rep reference as a `user_id`. Add the **Users** entity as a second source in your data flow and use the Join transformation to match `user_id` to the user's name and email.

</details>

### Rate limits

<details>

<summary>My sync is slow or stops partway through large entities</summary>

Close.com's API enforces rate limits, especially for large orgs with many leads or events. If you're syncing a high-volume entity like Events or Call activities, set a start date to limit the data range per run. For very large historical pulls, consider syncing in chunks by adjusting the start date across multiple data flows.

</details>

## Close.com 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](#close-com-data-overview). For help with sync errors or missing records, visit [Common Issues](#close-com-common-issues).
{% 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 by asking a question.

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

```
GET https://docs.coupler.io/sources/category/crm/close-com.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 `automate deployments from our CI pipeline` 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.
