Copper connector
Set up the Copper connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.
Copper connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Copper data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your CRM data instead of moving it.
What is the Copper connector
Section titled “What is the Copper connector”Sync your Copper CRM data into BigQuery with Kaivo to report on pipeline, accounts, and activity alongside the rest of your data.
| Category | CRM |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Copper connector
Section titled “Getting started with the Copper connector”- Sign up for Kaivo and create a workspace.
- Connect your Copper account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Copper
Section titled “Authenticating Copper”Authenticate with your API Key.
| Field | Description |
|---|---|
| API Key | |
| Your Copper API key. |
|
Configuring the Copper connector
Section titled “Configuring the Copper connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| User email | |
| Your Copper account email address. |
|
Tables and columns synced from Copper
Section titled “Tables and columns synced from Copper”Kaivo syncs 4 tables from Copper into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
companies (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
address__city |
STRING |
City of the company address |
address__country |
STRING |
Country of the company address |
address__postal_code |
STRING |
Postal code of the company address |
address__state |
STRING |
State of the company address |
address__street |
STRING |
Street address of the company |
assignee_id |
INT64 |
ID of the assignee for the company |
contact_type_id |
INT64 |
ID representing the contact type |
date_created |
INT64 |
Date when the company record was created |
date_modified |
INT64 |
Date when the company record was last modified |
details |
STRING |
Additional details about the company |
email_domain |
STRING |
Email domain associated with the company |
id |
INT64 |
Unique identifier for the company |
interaction_count |
INT64 |
Count of interactions with the company |
name |
STRING |
Name of the company |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: companies__custom_fields
Section titled “Subtable: companies__custom_fields”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: companies__phone_numbers
Section titled “Subtable: companies__phone_numbers”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: companies__socials
Section titled “Subtable: companies__socials”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
category |
STRING |
Category of the social media profile |
url |
STRING |
URL of the social media profile |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: companies__tags
Section titled “Subtable: companies__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
Tag item |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: companies__websites
Section titled “Subtable: companies__websites”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
category |
STRING |
Category of the website |
url |
STRING |
URL of the website |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
opportunities (20 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
assignee_id |
FLOAT64 |
The unique identifier of the user assigned to this opportunity. |
close_date |
STRING |
The expected or actual closing date of the opportunity. |
company_id |
STRING |
The unique identifier of the company associated with this opportunity. |
company_name |
STRING |
The name of the company associated with this opportunity. |
customer_source_id |
STRING |
The unique identifier of the source through which the customer was acquired. |
date_created |
INT64 |
The date and time when the opportunity was created. |
date_modified |
INT64 |
The date and time when the opportunity was last modified. |
details |
STRING |
Additional details or notes related to the opportunity. |
id |
INT64 |
The unique identifier of the opportunity. |
loss_reason_id |
STRING |
The unique identifier of the reason for losing the opportunity. |
monetary_value |
INT64 |
The potential or actual monetary value associated with the opportunity. |
name |
STRING |
The name or title of the opportunity. |
pipeline_id |
STRING |
The unique identifier of the pipeline to which the opportunity belongs. |
pipeline_stage_id |
STRING |
The unique identifier of the stage of the pipeline the opportunity is currently in. |
primary_contact_id |
STRING |
The unique identifier of the primary contact associated with the opportunity. |
priority |
STRING |
The priority level assigned to the opportunity. |
status |
STRING |
The current status of the opportunity (e.g., open, closed-won, closed-lost). |
win_probability |
FLOAT64 |
The probability of winning the opportunity expressed as a percentage. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: opportunities__tags
Section titled “Subtable: opportunities__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
A tag or label associated with the opportunity. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
people (25 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
address__city |
STRING |
The city where the person resides. |
address__country |
STRING |
The country where the person resides. |
address__postal_code |
STRING |
The postal code of the person’s address. |
address__state |
STRING |
The state or region where the person resides. |
address__street |
STRING |
The street address of the person. |
assignee_id |
INT64 |
ID of the assigned user or team. |
company_id |
INT64 |
ID of the company to which the person belongs. |
company_name |
STRING |
The name of the company the person is associated with. |
contact_type_id |
INT64 |
ID representing the type of contact (e.g., client, prospect). |
date_created |
INT64 |
The date when the person record was created. |
date_last_contacted |
INT64 |
The date of the last contact or interaction with the person. |
date_lead_created |
INT64 |
The date when the person was identified as a lead. |
date_modified |
INT64 |
The date when the person record was last updated. |
details |
JSON |
Additional details or notes about the person. |
first_name |
STRING |
The first name of the person. |
id |
INT64 |
Unique identifier for the person record. |
interaction_count |
INT64 |
The total number of interactions with the person. |
last_name |
STRING |
The last name of the person. |
middle_name |
STRING |
The middle name of the person. |
name |
STRING |
The full name of the person. |
prefix |
STRING |
A title or honorific preceding the person’s name (e.g., Mr., Dr., etc.). |
suffix |
STRING |
A title or honorific following the person’s name (e.g., Jr., III, etc.). |
title |
STRING |
The job title or role of the person. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__custom_fields
Section titled “Subtable: people__custom_fields”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__emails
Section titled “Subtable: people__emails”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
category |
STRING |
The category or type of email address (e.g., work, personal, etc.). |
email |
STRING |
The email address of the person. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__leads_converted_from
Section titled “Subtable: people__leads_converted_from”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__phone_numbers
Section titled “Subtable: people__phone_numbers”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
category |
STRING |
The category or type of phone number (e.g., mobile, office, etc.). |
number |
STRING |
The phone number of the person. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__socials
Section titled “Subtable: people__socials”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__tags
Section titled “Subtable: people__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: people__websites
Section titled “Subtable: people__websites”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
category |
STRING |
The category or type of website URL (e.g., personal, company, etc.). |
url |
STRING |
The URL of a website associated with the person. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
projects (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
assignee_id |
INT64 |
The unique identifier of the user assigned to the project. |
date_created |
INT64 |
The date when the project was created. |
date_modified |
INT64 |
The date when the project was last modified. |
details |
STRING |
Additional details or description of the project. |
id |
INT64 |
The unique identifier of the project. |
name |
STRING |
The name or title of the project. |
related_resource |
STRING |
Reference to any related resource linked to the project. |
status |
STRING |
The current status of the project. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: projects__custom_fields
Section titled “Subtable: projects__custom_fields”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: projects__tags
Section titled “Subtable: projects__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Copper sync works
Section titled “How the Copper sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Copper supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Copper?
Section titled “How long does the initial sync take for Copper?”It depends on how much history is in your Copper account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Copper’s schema changes?
Section titled “What happens when Copper’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Copper, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Copper instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Copper connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Copper data
Section titled “Common use cases for Copper data”Pipeline reporting
Section titled “Pipeline reporting”Track opportunities to see pipeline value, stage movement, and win rates.
Account view
Section titled “Account view”Join people with companies to understand your accounts and where activity sits.
Project tracking
Section titled “Project tracking”Use projects to follow work tied to your customers and deals.
Sales context
Section titled “Sales context”Bring Copper data into BigQuery to combine pipeline with revenue and marketing data.
Use Copper data in your AI and BI tools
Section titled “Use Copper data in your AI and BI tools”Once Copper data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Copper data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Copper connector pricing and plan details.