Linking Copper as a source
This source is currently in alpha. The interface and available tables may change.
Sync your Copper CRM data – people, companies, leads, opportunities, projects, tasks, and reference data – into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Copper.
- 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.
- Back in PostHog, enter the credentials and click Next.
- 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 | 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 | — |
users | A user (team member) in the Copper CRM account. | Full refresh | — | — |
pipelines | A sales pipeline defining the stages opportunities move through. | 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 | — | — |