Copper CRM integration | Zervanor
← All connectors

Copper CRM

Also an agent tool
sales-crm

Copper CRM automation across the Developer API v1: leads, people, companies, opportunities, projects, tasks, activities, related items, custom field definitions, pipelines/metadata reference lists, account, and users. API-key auth (3-header: X-PW-AccessToken + X-PW-Application + X-PW-UserEmail). Webhooks deferred for v1 (unsigned deliveries — no fitting signature handler; see compatibility.md copper-02).

53 actions · 1 triggers

The Copper CRM integration lets you connect Copper CRM to your automations with 53 actions and 1 triggers — and every action is also a tool an AI agent can call. Examples: Get Account, List Leads, Create Lead, Get Lead, Update Lead. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 1

Events in Copper CRM that can start a workflow.

polling

New/updated Copper person

Polls /people/search sorted by date_modified desc; de-dupes client-side by id (no server-side timestamp cursor — see copper-03). Fallback for the deferred unsigned webhooks (copper-02/copper-04).

Actions 53

What Zervanor can do in Copper CRM.

Companies6

POST

List Companies

List/search companies, paginated (POST /companies/search)

POST

Create Company

Create a new company (POST /companies)

GET

Get Company

Fetch a company by id (GET /companies/{id})

POST

Fetch Company By Email

Fetch a company by email (email in body) (POST /companies/fetch_by_email)

PUT

Update Company

Update a company (PUT /companies/{id})

DELETE

Delete Company

Delete a company (DELETE /companies/{id})

Leads6

POST

List Leads

List/search leads, paginated (POST /leads/search)

POST

Create Lead

Create a new lead (POST /leads)

GET

Get Lead

Fetch a lead by id (GET /leads/{id})

PUT

Update Lead

Update a lead (PUT /leads/{id})

DELETE

Delete Lead

Delete a lead (DELETE /leads/{id})

POST

Convert Lead

Convert a lead to a person/company/opportunity (POST /leads/{id}/convert)

People6

POST

List People

List/search people, paginated (POST /people/search)

POST

Create Person

Create a new person/contact (POST /people)

GET

Get Person

Fetch a person by id (GET /people/{id})

POST

Fetch Person By Email

Fetch a person by email (email in body) (POST /people/fetch_by_email)

PUT

Update Person

Update a person (PUT /people/{id})

DELETE

Delete Person

Delete a person (DELETE /people/{id})

Activities5

POST

List Activities

List/search activities, paginated (POST /activities/search)

POST

Create Activity

Create a new (user-type) activity (POST /activities)

GET

Get Activity

Fetch an activity by id (GET /activities/{id})

PUT

Update Activity

Update a (user-type) activity (PUT /activities/{id})

DELETE

Delete Activity

Delete a (user-type) activity (DELETE /activities/{id})

Opportunities5

POST

List Opportunities

List/search opportunities, paginated (POST /opportunities/search)

POST

Create Opportunity

Create a new opportunity (POST /opportunities)

GET

Get Opportunity

Fetch an opportunity by id (GET /opportunities/{id})

PUT

Update Opportunity

Update an opportunity (PUT /opportunities/{id})

DELETE

Delete Opportunity

Delete an opportunity (DELETE /opportunities/{id})

Projects5

POST

List Projects

List/search projects, paginated (POST /projects/search)

POST

Create Project

Create a new project (POST /projects)

GET

Get Project

Fetch a project by id (GET /projects/{id})

PUT

Update Project

Update a project (PUT /projects/{id})

DELETE

Delete Project

Delete a project (DELETE /projects/{id})

Tasks5

POST

List Tasks

List/search tasks, paginated (POST /tasks/search)

POST

Create Task

Create a new task (POST /tasks) — requires only name

GET

Get Task

Fetch a task by id (GET /tasks/{id})

PUT

Update Task

Update a task (PUT /tasks/{id})

DELETE

Delete Task

Delete a task (DELETE /tasks/{id})

Related3

GET

List Related Items

List all related items of an entity (GET /{resource}/{id}/related). resource ∈ leads|people|companies|opportunities|projects|tasks.

POST

Relate Item

Relate an existing record to an entity (POST /{resource}/{id}/related)

DELETE

Unrelate Item

Remove a relationship (DELETE /{resource}/{id}/related); related id/type in body

Users3

POST

List Users

List/search users, paginated (POST /users/search)

GET

Get User

Fetch a user by id (GET /users/{id})

POST

Fetch User By Email

Fetch a user by email (email in body) (POST /users/fetch_by_email)

Custom Field Definitions2

GET

List Custom Field Definitions

List all custom field definitions (GET /custom_field_definitions)

GET

Get Custom Field Definition

Fetch a single custom field definition (GET /custom_field_definitions/{id})

Account1

GET

Get Account

Fetch account details (id, name) — safe identity/connectivity check (GET /account)

Activity Types1

GET

List Activity Types

List activity types (GET /activity_types)

Contact Types1

GET

List Contact Types

List contact types (GET /contact_types)

Customer Sources1

GET

List Customer Sources

List customer sources (GET /customer_sources)

Loss Reasons1

GET

List Loss Reasons

List loss reasons (GET /loss_reasons)

Pipeline Stages1

GET

List Pipeline Stages

List all pipeline stages (GET /pipeline_stages)

Pipelines1

GET

List Pipelines

List opportunity pipelines (GET /pipelines)

Automations using Copper CRM

Build your own automation with Copper CRM in the visual builder.

Frequently asked questions

What can I automate with Copper CRM?

53 actions are available — for example: Get Account, List Leads, Create Lead, Get Lead, Update Lead, and more.

Which Copper CRM events can start a workflow?

1 triggers — for example: New/updated Copper person.

Can Copper CRM be used as an AI agent tool?

Yes. Every Copper CRM action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Copper CRM integration modelled?

Copper CRM is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.