Source connector

Copper connector

Copper integration for databases, warehouses and BI tools

Google Workspace-native CRM. Datrise captures Copper entities such as Google Workspace CRM entities, opportunities, and relationship timelines, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Copper Developer API v1 authenticates with API key, incremental runs key on date_modified, and Copper caps calls at 180 requests per minute per API key on a rolling window, plus a separate 3 requests per second cap on the bulk endpoints; both return HTTP 429.

Of the 3 objects, 3 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `copper_google_workspace_crm_entities`) with a schema derived from the Copper API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Copper pipeline page, and join the waitlist to get the Copper connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Copper data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
Google Workspace CRM entities	copper_google_workspace_crm_entities	Upsert by primary key, incremental on updated-at
opportunities	copper_opportunities	Upsert by primary key, incremental on updated-at
relationship timelines	copper_relationship_timelines	Upsert by primary key, incremental on updated-at

Copper API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	Copper Developer API v1
Authentication	API key — Three headers together: `X-PW-AccessToken` (the API key), `X-PW-Application: developer_api` and `X-PW-UserEmail` for the token owner; requests must use TLS 1.2 or higher.
Pagination	page — 1-indexed `page_number` with `page_size` (default 20, maximum 200) in the POST body of the /search endpoints; the `X-PW-TOTAL` response header gives an upper bound on matches.
Rate limit	180 requests per minute per API key on a rolling window, plus a separate 3 requests per second cap on the bulk endpoints; both return HTTP 429
Incremental cursor	date_modified — Incremental pulls are expressed as `sort_by: date_modified` with `sort_direction: desc` on the search endpoints; there is no since-parameter.
Webhooks	Yes — Copper webhook subscriptions (new / update / delete on Lead, Person, Company, Opportunity, Project, Task and activity_log)
Bulk export	No
Deletes detectable	Yes — The `delete` webhook event fires per entity type; the REST API itself exposes no deleted-records endpoint.

Official API reference

What bites when replicating Copper

Search results are capped at the first 100,000 records regardless of `page_number` and `page_size`, so a large tenant has to be sliced into date_modified windows rather than paged straight through.
The 180 requests/minute limit is not exposed in any response header, so a client has to count its own calls to stay under it.
Webhook notifications fire at most once per event and are never retried, and each carries up to 30 record IDs — a missed delivery is only recoverable by re-polling.
`page_size` defaults to 20, so a client that leaves it alone makes ten times more calls than necessary against that 180/minute budget.

Compare this against every other documented API

Popular destinations for Copper

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Copper connector FAQ

What Copper data does the connector extract?: 3 objects: Google Workspace CRM entities, opportunities and relationship timelines. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Copper integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Copper data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Copper → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Copper pipeline with guided onboarding

Join the waitlist to get priority access for Copper integrations with guided setup, schema-aware mapping, and production-grade incremental sync.