# Copper CRM

### Snapshot

| Features                        | Details                                      |
| ------------------------------- | -------------------------------------------- |
| Release Status                  | Released                                     |
| Source API Version              | v1                                           |
| Table Selection                 | Yes                                          |
| Column Selection                | Yes                                          |
| Edit Integration                | Yes                                          |
| Replication Type Selection      | No                                           |
| Authentication Parameters       | <p>Email as Username</p><p>Access Token </p> |
| Replication Type                | Key Based Replication                        |
| Replication Key                 | Modified\_Date,Activity\_Date                |
| Suggested Replication Frequency | 1 hr                                         |

| Tables/APIs Supported |               |
| --------------------- | ------------- |
| People                | Users         |
| Companies             | Opportunities |
| Leads                 | Activities    |

Activities

### Integrate CopperCRM with Daton

1. Signin to Daton&#x20;
2. Select CopperCRM from Integrations page
3. Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later&#x20;
4. Provide Email as username and Access Token to authorize Daton to periodically extract data from CopperCRM
5. Post successful authentication, you will be prompted to choose from the list of available tables
6. Then select all required fields for each table
7. Submit the integration

### Workflow

1. Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
2. Users would be able to edit/pause/re-activate/delete integration anytime
3. Users can view job status and process logs from the integration details page by clicking on the integration name from the active list

### CopperCRM Data

**People**

Purpose: A Person is an individual with whom you communicate. The People API allows you to create, view, delete and update your People. You can retrieve an individual Person, list all People, or use search filters to view subsets of your People.

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Key-Based Replication

Replication Key: Created\_Date

**Fields**

| Name                  | Target Datatype |
| --------------------- | --------------- |
| id                    | NUMERIC         |
| Name                  | STRING          |
| First\_name           | STRING          |
| Last\_name            | STRING          |
| Address               | RECORD          |
| Assignee\_id          | NUMERIC         |
| Contact\_type\_id     | NUMERIC         |
| Email                 | RECORD          |
| phone\_numbers        | RECORD          |
| Socials               | RECORD          |
| Websites              | RECORD          |
| Custom\_fields        | RECORD          |
| Date\_created         | NUMERIC         |
| Date\_Modified        | NUMERIC         |
| Date\_Last\_Connected | NUMERIC         |
| Interaction\_count    | NUMERIC         |
| Company\_id           | NUMERIC         |
| Company\_name         | STRING          |
| Middle\_name          | STRING          |

**Users**

Purpose: To list the users with their id's,name and email

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Full Replication

Replication Key: NA

**Fields**

| Name  | Target Datatype |
| ----- | --------------- |
| Id    | NUMERIC         |
| Name  | STRING          |
| Email | STRING          |

**Companies**

Purpose: A Company is an organization with which you communicate. The Companies API allows you to create, view, delete and update your Companies. You can retrieve individual Companies, list all Companies, or use search filters to view subsets of your Companies

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Full Replication

Replication Key: NA

**Fields**

| Name               | Target Datatype |
| ------------------ | --------------- |
| Id                 | Numeric         |
| Name               | STRING          |
| Assignee\_id       | NUMERIC         |
| Contact\_type\_id  | NUMERIC         |
| Details            | STRING          |
| Email\_Domain      | STRING          |
| Socials            | RECORD          |
| Websites           | RECORD          |
| Custom\_Fields     | RECORD          |
| Interaction\_Count | NUMERIC         |
| Date\_Created      | NUMERIC         |
| Date\_Modified     | NUMERIC         |

**Opportunities**

Purpose: An Opportunity is a potential business deal. The Opportunities API allows you to create, view, delete and update your Opportunities.&#x20;

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Key-Based Replication

Replication Key: Modified\_Date

**Fields**

| Id                    | NUMERIC |
| --------------------- | ------- |
| Name                  | STRING  |
| Assignee\_id          | NUMERIC |
| Close\_Date           | STRING  |
| Pipeline\_id          | NUMERIC |
| Pipeline\_stage\_id   | NUMERIC |
| Primary\_Contact\_id  | NUMERIC |
| Priority              | STRING  |
| Status                | STRING  |
| Interaction\_count    | NUMERIC |
| Monetary\_unit        | STRING  |
| Monetary\_Value       | NUMERIC |
| Win\_Probability      | NUMERIC |
| Date\_Stage\_Changed  | NUMERIC |
| Date\_Last\_Contacted | NUMERIC |
| Date\_Created         | NUMERIC |
| Date\_Modified        | NUMERIC |
| Custom\_Fields        | RECORD  |
| Company\_id           | NUMERIC |
| Company\_Name         | STRING  |
| Loss\_Reason\_id      | NUMERIC |

**Activities**

Purpose: Copper keeps a record of activities for People, Leads, Opportunities, and Companies. The Activities API allows you to view, create, edit, and delete activities

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Key-Based Replication

Replication Key: Activity\_Date

**Fields**

| Id             | NUMERIC |
| -------------- | ------- |
| Parent         | RECORD  |
| Type           | RECORD  |
| user\_id       | NUMERIC |
| Details        | STRING  |
| Activity\_Date | NUMERIC |
| Old\_value     | RECORD  |
| New\_value     | RECORD  |
| Date\_Created  | NUMERIC |
| Date\_Modified | NUMERIC |
| Old\_value\_st | STRING  |
| New\_value\_st | STRING  |

**Leads**

Purpose: A Lead is an individual or a company that's interested in your products or services.

Source API Documentation &#x20;

<https://developer.copper.com/index.html>

Replication: Full Replication

Replication Key: NA

**Fields**

| Name                  | Target Datatype |
| --------------------- | --------------- |
| id                    | Numeric         |
| name                  | STRING          |
| First\_name           | STRING          |
| Last\_name            | STRING          |
| Address               | RECORD          |
| Assignee\_id          | NUMERIC         |
| Details               | STRING          |
| Email                 | RECORD          |
| Interaction\_count    | NUMERIC         |
| Socials               | RECORD          |
| Status                | STRING          |
| Status\_id            | NUMERIC         |
| Websites              | RECORD          |
| Custom\_fields        | RECORD          |
| Date\_created         | NUMERIC         |
| Date\_Modified        | NUMERIC         |
| Date\_Last\_Contacted | NUMERIC         |


---

# Agent Instructions: 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:

```
GET https://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/saas-integrations/copper-crm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.