> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Copper as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/copper

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

Sync your Copper CRM data – people, companies, leads, opportunities, projects, tasks, and reference data – into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Copper.
3.  Next, gather your Copper credentials:
    -   **API key** – generate one in Copper under **Settings → Integrations → API Keys**.
    -   **User email** – the email address of the user the API key belongs to.
4.  Back in PostHog, enter the credentials and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Copper data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `people` | Individual contacts in your Copper account | Incremental |
| `companies` | Company records | Incremental |
| `leads` | Sales leads | Incremental |
| `opportunities` | Sales opportunities (deals) | Incremental |
| `projects` | Projects | Incremental |
| `tasks` | Tasks | Incremental |
| `users` | Users in your Copper account | Full refresh |
| `pipelines` | Pipeline definitions | Full refresh |
| `customer_sources` | Customer source reference data | Full refresh |
| `loss_reasons` | Loss reason reference data | Full refresh |
| `contact_types` | Contact type reference data | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

Incremental tables sync on the `date_modified` or `date_created` field (both Unix epoch seconds). The `users` table and the reference tables (`pipelines`, `customer_sources`, `loss_reasons`, `contact_types`) have no reliable server-side timestamp filter and are full refresh only.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `User email` | email | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `people` | A person contact stored in Copper CRM. | Incremental, Full refresh | date\_modified, date\_created | — |
| `companies` | A company (organization) stored in Copper CRM. | Incremental, Full refresh | date\_modified, date\_created | — |
| `leads` | An unqualified prospect (lead) stored in Copper CRM. | Incremental, Full refresh | date\_modified, date\_created | — |
| `opportunities` | A potential sale (opportunity) tracked through a pipeline in Copper CRM. | Incremental, Full refresh | date\_modified, date\_created | — |
| `projects` | A project used to organize work after a deal closes in Copper CRM. | Incremental, Full refresh | date\_modified, date\_created | — |
| `tasks` | A to-do item (task) associated with CRM records in Copper. | Incremental, Full refresh | date\_modified, date\_created | — |
| `activities` | An entry in the Copper interaction log: a user-entered note, call or meeting, or a system-generated record of a property or pipeline stage change. | Incremental, Full refresh | activity\_date | — |
| `users` | A user (team member) in the Copper CRM account. | Full refresh | — | — |
| `pipelines` | A sales pipeline defining the stages opportunities move through. | Full refresh | — | — |
| `pipeline_stages` | A stage within a sales pipeline, defining where an opportunity sits in that pipeline. | Full refresh | — | — |
| `customer_sources` | A reference list of customer sources used to attribute where leads and opportunities came from. | Full refresh | — | — |
| `loss_reasons` | A reference list of reasons used to record why an opportunity was lost. | Full refresh | — | — |
| `contact_types` | A reference list of contact types used to classify people and companies. | Full refresh | — | — |
| `lead_statuses` | A reference list of statuses marking where a lead sits in the qualification process. | Full refresh | — | — |
| `custom_activity_types` | An activity type created for the account, with the display settings the app uses for it. | Full refresh | — | — |
| `activity_types` | A reference list of the activity types in the account. Types in the user category are user-entered (notes, calls, meetings and any custom types); types in the system category are generated by Copper. | Full refresh | — | — |
| `custom_field_definitions` | A custom field configured for the account, describing what the matching entry in a record's custom\_fields holds. | Full refresh | — | — |
| `tags` | A tag used in the account, with how many records of each type carry it. Tags have no id, so the name identifies the row. | Full refresh | — | — |
| `field_layouts` | One field of one record type's layout, saying which fields apply to that record type and in what order. Configured in Copper under Settings, Manage Fields On Records. | Full refresh | — | — |
| `related_items` | One link between two Copper records, as shown in the Related Items section of the app. Links are bidirectional, so each link appears twice, once from each end. | Full refresh | — | — |