Copper connector for AI agents

Tools your sales agent reaches for on Copper, scoped per user.

CALL ANY TOOL

69 tools for CRM in Copper: search, create, and update leads, people, companies, and opportunities, log activities, manage tasks and projects, and link related records.

copper_account_get

Get account

Get details of the Copper account the API key belongs to. Returns the account id, name, primary timezone and settings such as whether leads and team permissions are enabled. Use it to check the connection or read account settings. Use copper_current_user_get for the API user.

Parameters

Name

Type

Required

Description

—

No parameters required

copper_activities_search

Search activities

copper_activity_create

Create activity

copper_activity_delete

Delete activity

copper_activity_types_list

List activity types

copper_activity_update

Update activity

copper_company_get

Get company

copper_connect_field_link_create

Create connect field link

copper_connect_field_link_delete

Delete connect field link

copper_contact_types_list

List contact types

copper_custom_activity_type_get

Get custom activity type

copper_customer_sources_list

List customer sources

copper_field_layout_get

Get field layout

copper_lead_convert

Convert lead

copper_lead_delete

Delete lead

copper_lead_get

Get lead

copper_lead_statuses_list

List lead statuses

copper_lead_update

Update lead

Update fields on an existing lead in Copper; fields you leave out stay unchanged. Returns the updated lead record. Use it to edit a lead you have the ID for. Use copper_lead_upsert to update-or-create by matching criteria, and copper_lead_convert to turn it into a person.

Parameters

Name

Type

Required

Description

lead_id

integer

Required

ID of the lead. Get it from copper_leads_search. Example: 8900677.

address

object

Optional

Postal address of the lead, as an object with street, city, state, postal_code and country (all strings, all optional). Example: {"street": "123 Main Street", "city": "Savannah", "state": "Georgia", "postal_code": "31410", "country": "United States"}.

assignee_id

integer

Optional

ID of the Copper user who owns the lead. Get user IDs from copper_users_list. Example: 137658.

company_name

string

Optional

Name of the company the lead works for. Example: "Acme Inc".

custom_fields

array

Optional

Custom field values for the lead. Each item has a custom_field_definition_id (from copper_custom_field_definitions_list) and a value: a string, a number, a Unix timestamp for dates, an option id for dropdowns, or a list of option ids for multi-selects. Example: [{"custom_field_definition_id": 100764, "value": "Referral"}].

customer_source_id

integer

Optional

Customer source that generated the lead, from copper_customer_sources_list. Example: 331242.

details

string

Optional

Free-text description or notes for the lead. Example: "Met at the Austin trade show".

object

Optional

Email of the lead, as an object with email and category (work, personal or other). Example: {"email": "jane@acme.com", "category": "work"}.

monetary_value

number

Optional

Expected monetary value of business with the lead. Example: 5000.

name

string

Optional

New full name of the lead. Example: "Jane Doe".

phone_numbers

array

Optional

Phone numbers of the lead. Each item has a number and a category such as work, mobile, home or other. Example: [{"number": "415-123-4567", "category": "work"}].

socials

array

Optional

Social profiles of the lead. Each item has a url and a category such as linkedin, twitter or facebook. Example: [{"url": "https://www.linkedin.com/in/janedoe", "category": "linkedin"}].

status

string

Optional

Lead status. One of New, Unqualified, Contacted, Qualified. Example: "New". One of: `New`, `Unqualified`, `Contacted`, `Qualified`.

tags

array

Optional

Tags to put on the lead, as plain strings. On update this replaces the record's whole tag list. Example: ["enterprise", "q3"].

title

string

Optional

Job title of the lead. Example: "Head of Operations".

websites

array

Optional

Websites of the lead. Each item has a url and a category such as work or personal. Example: [{"url": "https://www.acme.com", "category": "work"}].

copper_lead_upsert

Upsert lead

copper_leads_search

Search leads

Search leads in Copper by name, email, phone, status, source, owner, value, location, tags, dates or custom fields; all filters combine with AND. Returns a page of lead records with id, name, company name, email, status, monetary value, owner, tags and custom fields. Use it to list or find leads. Use copper_lead_get when you already have the lead ID. Converted leads are excluded unless include_converted_leads is true.

Parameters

Name

Type

Required

Description

age

integer

Optional

Maximum age of the lead record, in seconds. Example: 86400.

assignee_ids

array

Optional

Only leads owned by these users. Get IDs from copper_users_list. Use -2 for leads with no owner. Example: [137658].

city

string

Optional

City the lead must be located in. Example: "Austin".

country

string

Optional

Two-letter country code the lead must be located in. Example: "US".

custom_fields

array

Optional

Filter by custom field values (text fields can't be searched). Each item has a custom_field_definition_id plus either value (a list of option ids for dropdown and multi-select fields, true or false for checkboxes, a number for number fields), or minimum_value and maximum_value for date, percentage and currency ranges. Add allow_empty: true to also match records where a dropdown or multi-select field is empty. Example: [{"custom_field_definition_id": 10, "value": [3]}].

customer_source_ids

array

Optional

Only leads from these customer sources. Get IDs from copper_customer_sources_list. Use -2 for leads with no source. Example: [331242].

emails

string

Optional

Email address of the lead. Example: "jane@acme.com".

followed

integer

Optional

Filter by whether the API user follows the lead: 1 = followed, 2 = not followed. Example: 1. One of: `1`, `2`.

ids

array

Optional

Only return these lead IDs. Get IDs from earlier search results. Example: [8900677].

include_converted_leads

boolean

Optional

Set true to also return leads that were already converted. Copper's default is false. Example: true.

maximum_created_date

integer

Optional

Only leads created on or before this time, as a Unix timestamp in seconds. Example: 1735689600.

maximum_interaction_count

integer

Optional

Only leads with at most this many interactions. Example: 10.

maximum_interaction_date

integer

Optional

Latest date of the last interaction with the leads, as a Unix timestamp in seconds. Example: 1735689600.

maximum_modified_date

integer

Optional

Only leads modified on or before this time, as a Unix timestamp in seconds. Example: 1735689600.

maximum_monetary_value

number

Optional

Only leads worth at most this amount. Example: 50000.

minimum_created_date

integer

Optional

Only leads created on or after this time, as a Unix timestamp in seconds. Example: 1704067200.

minimum_interaction_count

integer

Optional

Only leads with at least this many interactions. Example: 1.

minimum_interaction_date

integer

Optional

Earliest date of the last interaction with the leads, as a Unix timestamp in seconds. Example: 1704067200.

minimum_modified_date

integer

Optional

Only leads modified on or after this time, as a Unix timestamp in seconds. Example: 1704067200.

minimum_monetary_value

number

Optional

Only leads worth at least this amount. Example: 1000.

name

string

Optional

Full name of the lead to search for. Example: "Jane Doe".

page_number

integer

Optional

Page of results to return, starting at 1. Combine with page_size to page through results; stop when a page has fewer records than page_size. Example: 1.

page_size

integer

Optional

Number of records per page, from 1 to 200. Copper's default is 20. Example: 50.

phone_number

string

Optional

Phone number to match. Example: "4155551234".

postal_code

string

Optional

Postal code the lead must be located in. Example: "78701".

socials

array

Optional

Only leads with at least one of these social profile URLs. Example: ["https://www.linkedin.com/in/janedoe"].

sort_by

string

Optional

Field to sort the results by. Copper's default is name. Example: "date_modified". One of: `name`, `company_name`, `title`, `value`, `email`, `phone`, `date_modified`, `date_created`, `city`, `state`, `country`, `zip`, `inactive_days`, `socials`.

sort_direction

string

Optional

Sort direction: asc or desc. Copper's default is asc. Example: "desc". One of: `asc`, `desc`.

state

string

Optional

State or province the lead must be located in. Example: "TX".

status_ids

array

Optional

Only leads with these statuses. Get IDs from copper_lead_statuses_list. Example: [1].

tags

array

Optional

Only leads with at least one of these tags. Example: ["webinar"].

copper_people_search

Search people

Search people (contacts) in Copper by name, email, phone, company, owner, location, tags, dates or custom fields; all filters combine with AND. Returns a page of person records with id, name, emails, phone numbers, company, owner, tags and custom fields. Use it to list or find people. Use copper_person_get when you have the ID and copper_person_get_by_email for an exact email.

Parameters

Name

Type

Required

Description

age

integer

Optional

Maximum age of the person record, in seconds. Example: 86400 for records created in the last day.

assignee_ids

array

Optional

Only people owned by these users. Get IDs from copper_users_list. Use -2 for people with no owner. Example: [137658].

city

string

Optional

City the person must be located in. Example: "Austin".

company_ids

array

Optional

Only people belonging to these companies. Get IDs from copper_companies_search. Use -2 for people with no company. Example: [1234567].

contact_type_ids

array

Optional

Only people with these contact types. Get IDs from copper_contact_types_list. Example: [1].

country

string

Optional

Two-letter country code the person must be located in. Example: "US".

custom_fields

array

Optional

emails

array

Optional

Email addresses to match. Example: ["jane@acme.com"].

followed

integer

Optional

Filter by whether the API user follows the person: 1 = followed, 2 = not followed. Example: 1. One of: `1`, `2`.

ids

array

Optional

Only return these person IDs. Get IDs from earlier search results. Example: [27140359].

maximum_created_date

integer

Optional

Only people created on or before this time, as a Unix timestamp in seconds. Example: 1735689600.

maximum_interaction_count

integer

Optional

Only people with at most this many interactions. Example: 10.

maximum_interaction_date

integer

Optional

Latest date of the last interaction with the people, as a Unix timestamp in seconds. Example: 1735689600.

minimum_created_date

integer

Optional

Only people created on or after this time, as a Unix timestamp in seconds. Example: 1704067200.

minimum_interaction_count

integer

Optional

Only people with at least this many interactions. Example: 1.

minimum_interaction_date

integer

Optional

Earliest date of the last interaction with the people, as a Unix timestamp in seconds. Example: 1704067200.

name

string

Optional

Full name of the person to search for. Example: "Jane Doe".

opportunity_ids

array

Optional

Only people linked to these opportunities. Get IDs from copper_opportunities_search. Example: [2827698].

page_number

integer

Optional

Page of results to return, starting at 1. Combine with page_size to page through results; stop when a page has fewer records than page_size. Example: 1.

page_size

integer

Optional

Number of records per page, from 1 to 200. Copper's default is 20. Example: 50.

phone_number

string

Optional

Phone number to match. Non-digits are stripped; 7+ digits use fuzzy matching. Example: "4155551234".

postal_code

string

Optional

Postal code the person must be located in. Example: "78701".

socials

array

Optional

Only people with at least one of these social profile URLs. Example: ["https://www.linkedin.com/in/janedoe"].

sort_by

string

Optional

Field to sort the results by. Copper's default is first_name. Example: "date_modified". One of: `name`, `title`, `email`, `phone`, `date_modified`, `date_created`, `city`, `state`, `country`, `zip`, `socials`.

sort_direction

string

Optional

Sort direction: asc or desc. Copper's default is asc. Example: "desc". One of: `asc`, `desc`.

state

string

Optional

State or province the person must be located in. Example: "TX".

tags

array

Optional

Only people with at least one of these tags. Example: ["enterprise"].

copper_person_create

Create person

Create a person (contact) in Copper. Returns the new person record with its id. Use it to add a contact. The request fails if another person already has one of the emails; check first with copper_person_get_by_email. Use copper_lead_create for unqualified prospects.

Parameters

Name

Type

Required

Description

name

string

Required

Full name of the person. Example: "Jane Doe".

address

object

Optional

Postal address of the person, as an object with street, city, state, postal_code and country (all strings, all optional). Example: {"street": "123 Main Street", "city": "Savannah", "state": "Georgia", "postal_code": "31410", "country": "United States"}.

assignee_id

integer

Optional

ID of the Copper user who owns the person. Get user IDs from copper_users_list. Example: 137658.

company_id

integer

Optional

ID of the company the person belongs to, from copper_companies_search. Example: 1234567.

company_name

string

Optional

Name of the person's company, used when you don't have a company ID. Example: "Acme Inc".

contact_type_id

integer

Optional

Contact type of the person, from copper_contact_types_list. Example: 1.

custom_fields

array

Optional

Custom field values for the person. Each item has a custom_field_definition_id (from copper_custom_field_definitions_list) and a value: a string, a number, a Unix timestamp for dates, an option id for dropdowns, or a list of option ids for multi-selects. Example: [{"custom_field_definition_id": 100764, "value": "Referral"}].

details

string

Optional

Free-text description or notes for the person. Example: "Met at the Austin trade show".

emails

array

Optional

Email addresses of the person. Each item has an email and a category such as work, personal or other. Email must be unique across people. Example: [{"email": "jane@acme.com", "category": "work"}].

phone_numbers

array

Optional

Phone numbers of the person. Each item has a number and a category such as work, mobile, home or other. Example: [{"number": "415-123-4567", "category": "work"}].

socials

array

Optional

Social profiles of the person. Each item has a url and a category such as linkedin, twitter or facebook. Example: [{"url": "https://www.linkedin.com/in/janedoe", "category": "linkedin"}].

tags

array

Optional

Tags to put on the person, as plain strings. Example: ["enterprise", "q3"].

title

string

Optional

Job title of the person. Example: "VP of Sales".

websites

array

Optional

Websites of the person. Each item has a url and a category such as work or personal. Example: [{"url": "https://www.acme.com", "category": "work"}].

copper_person_delete

Delete person

copper_person_get

Get person

copper_person_update

Update person

Update fields on an existing person (contact) in Copper; fields you leave out stay unchanged. Returns the updated person record. Use it to edit a contact. To change the person's company, use copper_related_item_remove and copper_related_item_add instead. Get the ID from copper_people_search.

Parameters

Name

Type

Required

Description

person_id

integer

Required

ID of the person. Get it from copper_people_search. Example: 27140359.

address

object

Optional

assignee_id

integer

Optional

ID of the Copper user who owns the person. Get user IDs from copper_users_list. Example: 137658.

contact_type_id

integer

Optional

Contact type of the person, from copper_contact_types_list. Example: 1.

custom_fields

array

Optional

Custom field values to set on the person. Each item has a custom_field_definition_id and a value. Only send the fields you are changing: connect fields read back as [] and sending [] removes their connections. Example: [{"custom_field_definition_id": 100764, "value": "Referral"}].

details

string

Optional

Free-text description or notes for the person. Example: "Met at the Austin trade show".

emails

array

Optional

Email addresses of the person. Each item has an email and a category such as work, personal or other. Email must be unique across people. Example: [{"email": "jane@acme.com", "category": "work"}].

name

string

Optional

New full name of the person. Example: "Jane Doe".

phone_numbers

array

Optional

Phone numbers of the person. Each item has a number and a category such as work, mobile, home or other. Example: [{"number": "415-123-4567", "category": "work"}].

socials

array

Optional

Social profiles of the person. Each item has a url and a category such as linkedin, twitter or facebook. Example: [{"url": "https://www.linkedin.com/in/janedoe", "category": "linkedin"}].

tags

array

Optional

Tags to put on the person, as plain strings. On update this replaces the record's whole tag list. Example: ["enterprise", "q3"].

title

string

Optional

Job title of the person. Example: "VP of Sales".

websites

array

Optional

Websites of the person. Each item has a url and a category such as work or personal. Example: [{"url": "https://www.acme.com", "category": "work"}].

copper_pipeline_stages_in_pipeline_list

List pipeline stages in pipeline

copper_project_get

Get project

copper_related_item_add

Add related item

copper_related_item_remove

Remove related item

copper_related_items_by_type_list

List related items by type

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Copper tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["copper"], toolNames: [
    "copper_opportunities_search",
    "copper_opportunity_update",
    "copper_activity_create"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Move Northwind Renewal to Negotiation and log today's call" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["copper"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Move Northwind Renewal to Negotiation and log today's call" }],
  tools,
});

// Execute the tool call with the user's vaulted Copper API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["copper"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Move Northwind Renewal to Negotiation and log today's call" }],
  tools,
});

// Tool call runs with the user's vaulted Copper API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["copper"] }, pageSize: 100,
});

const agent = new Agent({
  name: "sales_agent",
  model: "gemini-2.5-pro",
  instruction: "Copper tools scoped to this user",
  tools,
});

await agent.run("Move Northwind Renewal to Negotiation and log today's call");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Copper tool. Click to copy, paste into your agent, done.

Pipeline

Copy the prompt

Copied

List open opportunities in the Sales pipeline closing this month.

Copy the prompt

Copied

Move the Northwind Renewal opportunity to Negotiation.

Copy the prompt

Copied

Create an opportunity for Acme Corp worth $40,000.

Leads and contacts

Copy the prompt

Copied

Find the person with the email jane@northwind.com.

Copy the prompt

Copied

Convert the lead Priya Shah into a person with a new opportunity.

Copy the prompt

Copied

Create a lead for Sam Ortiz from the webinar.

Activity and tasks

Copy the prompt

Copied

Log a call note on Acme Corp from today's check-in.

Copy the prompt

Copied

Create a follow-up task for the Northwind Renewal due Friday.

Copy the prompt

Copied

Show the last 10 activities on Northwind.

SEE HOW AUTH WORKS

Each user connects their own Copper API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Copper

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Copper

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Copper

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Copper

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other CRM and sales connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

GTM and RevOps Teams

Sales call prep agent

Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Copper API key looks fine in a demo. In production every record change looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Copper today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Copper as the user or through a shared key?

As the user. Each user connects their own Copper API key once, and Scalekit sends it with every call. Audit logs attribute every record change and logged activity to that user, not a shared service account.

Where is the Copper API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Copper?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example search and logging tools without copper_company_delete or copper_opportunity_delete, which permanently delete records. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Copper access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent work with custom fields in Copper?

Yes. copper_custom_field_definitions_list returns the custom field definitions in the account, and copper_field_layout_get shows which standard and custom fields appear on each record type. copper_lead_upsert can match a lead by name, email, or a custom field.