> 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/data-overview.md).

# 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


---

# 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/data-overview.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.