Copper is a customer relationship management platform for managing contacts, companies, leads, opportunities, projects, tasks, activities, files, and webhooks.
Attempt to create 1-10 user-category Copper activities and return ordered per-item successes or validation failures. Deleting these activities is a soft delete: successful cleanup may leave an activity fetchable as an is_deleted=true stub rather than make it fully disappear. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Attempt to create 1-10 Copper companies and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Create 1-10 Copper leads in one beta bulk request and return ordered per-item outcomes. Copper can return HTTP 500 after applying the write; treat failures as indeterminate and read records back before retrying to avoid duplicates.
Attempt to create 1-10 Copper opportunities and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Attempt to create 1-10 Copper people and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Attempt to update 1-10 Copper companies and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Update 1-10 Copper leads in one beta bulk request and return ordered per-item outcomes. Copper can return HTTP 500 after applying the write; treat failures as indeterminate and read records back before retrying.
Attempt to update 1-10 Copper people and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second.
Convert a Copper lead into a person and optionally a company and opportunity; the original lead is removed.
Create a user-category activity such as a note on an existing Copper lead, person, company, opportunity, project, or task; system activities are read-only.
Create a Copper company with domain, contact, ownership, tag, and custom-field data.
Create a named Copper custom activity type with a supported icon. Custom activity types cannot be deleted; retire one with UPDATE_CUSTOM_ACTIVITY_TYPE using is_disabled=true.
Create a Copper custom field for selected record types.
Create a Copper lead with contact, ownership, source, status, tag, and custom-field data.
Create a Copper opportunity. Only the name is required; Copper can supply the default pipeline and stage, and the primary contact is optional.
Create a Copper person with contact, company, ownership, tag, and custom-field data.
Create a Copper project, optionally related to another record and assigned to a user.
Connect two existing Copper records through a Connect custom field.
Create a Copper task with optional assignment, related record, due/reminder times, priority, tags, and custom fields.
Permanently delete one file attached to a Copper lead, person, opportunity, company, or project.
Permanently delete one Copper custom-field definition by ID.
Permanently delete one Copper lead by ID.
Delete one Copper person, company, opportunity, project, task, or activity by type and ID. Deleting an activity is a soft delete: successful cleanup may leave it fetchable as an is_deleted=true stub rather than make it fully disappear.
Delete one Copper Connect-field connection by related-link ID.
Return the connected Copper account, timezone, and feature settings; use it to preflight features such as Leads.
Get metadata for one file attached to a Copper lead, person, opportunity, company, or project.
Return the Copper user represented by the connected account, including the user ID used for assignments.
Return one Copper custom activity type's name, icon, enabled state, interaction behavior, and ownership metadata by ID.
Return one Copper custom field's data type, record availability, filterability, options, and currency configuration by definition ID.
Return enabled and create/edit requiredness metadata for one Copper entity type. Opportunities require pipeline_id; other entity types do not accept it.
Return one Copper lead's contact, ownership, source, status, tags, and custom-field data by lead ID.
Return the unique Copper person record matching an exact email address.
Fetch one user, person, company, opportunity, project, task, or activity by its type and ID.
List all files attached to one Copper lead, person, opportunity, company, or project.
List Copper's default user-entered activity types and account-created custom activity types; system activity types and Notes are available through LIST_REFERENCE_VALUES with activity_types.
Return Copper custom-field IDs, types, availability, and options needed to read, filter, and write custom field values.
List Copper lead status IDs, names, display order, and default selection for use in lead writes and searches.
List selected activity types related to one Copper lead, person, or company; company results may also include activities from related people.
List Copper opportunity stages for one pipeline, or omit pipeline_id for a flat cross-pipeline list; use LIST_PIPELINES when pipeline context and win probabilities are needed.
Return all configured Copper pipelines with their stages and win probabilities for opportunity creation and updates.
List one bounded set of Copper IDs used in write schemas: activity types, customer sources, contact types, or opportunity loss reasons.
List Connect-field connections for one Copper source record, optionally narrowed to one Connect field.
List records related to one Copper entity, optionally restricted to a target record type.
Return one alphabetical page of Copper tag names for filtering or assigning records.
Return one page of Copper users for resolving assignee and owner IDs.
Create a direct relationship between two existing Copper records, preserving both record types and IDs.
Search Copper activities globally or for one parent record by activity type and date range, returning one page.
Search Copper companies by name, domain, ownership, contact type, location, date, or custom-field criteria and return one page.
Search Copper leads by identity, ownership, status, source, location, value, activity, date, tags, socials, or custom fields and return one page.
Search Copper opportunities by pipeline, stage, status, contact, company, value, date, ownership, or custom-field criteria and return one page.
Search Copper people by contact, company, ownership, tag, date, or custom-field criteria and return one page.
Search Copper projects by name, owner, tag, status, or custom-field criteria and return one page.
Search Copper tasks by name, owner, tag, related project or opportunity, status, due date, or custom-field criteria and return one page.
Remove a direct relationship between two existing Copper records without deleting either record.
Update the details, date, or both for an existing user-category Copper activity; at least one change is required, and system or deleted activities cannot be modified.
Update selected writable fields of an existing Copper company without replacing omitted fields.
Rename, change the icon, or enable or disable a Copper custom activity type. To retire a type, disable it with is_disabled=true; custom activity types cannot be deleted.
Update one Copper custom-field definition by ID.
Update selected fields of a Copper lead without replacing omitted fields.
Update selected writable fields of an existing Copper opportunity without replacing omitted fields.
Update selected writable fields of an existing Copper person without replacing omitted fields.
Update selected writable fields of an existing Copper project without replacing omitted fields.
Update selected writable fields of an existing Copper task without replacing omitted fields.
Get upload authorization from Copper, upload up to 20 MB of file bytes to Copper's fixed Amazon S3 bucket, and attach the uploaded key to one Copper lead, person, opportunity, company, or project. If a failure occurs after the S3 upload starts, the file may already be uploaded or attached; verify the record before retrying to avoid duplicate attachments.
Create or update a Copper lead by exact name, email, or custom-field match. Copper resolves matches through a search index that can lag recent writes by seconds, so upserting a just-created lead may insert a duplicate; wait and verify before retrying. Copper rejects ambiguous matches.
The Copper integration connects your Dench AI CRM directly to Copper, so agents can read and act on your Copper data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
65 actions are available for agents to invoke on your behalf. Every call runs through Copper's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Copper and click Connect — you'll authorize access through Copper's own sign-in flow. No API keys or code required.
Ask an agent to use Copper in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Copper integration connects your AI CRM to Copper, so AI agents can work with your Copper data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Copper integration currently exposes 65 actions, including Bulk Create Activities (Beta), Bulk Create Companies (Beta), Bulk Create Leads, Bulk Create Opportunities (Beta), Bulk Create People (Beta), and Bulk Update Companies (Beta). Agents invoke them on your behalf from chat or from automations.
No. You connect Copper from your Dench workspace using Copper's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Copper's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Copper connection from your workspace settings at any time.