Copper
Keep Copper up to date with every customer, deal and order, without copy and paste.
34 ways to read, 15 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Copper, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Log activityApproval by rule
- Create companyApproval by rule
- Search activitiesRead
Example flow
- Copper · Search activitiesDone
- Copper · Log activityNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Copper.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Copper
- Copper's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Copper people, companies, opportunities, leads, tasks, activities and projects with custom fields, plus lead upsert, related records, file metadata, field layouts, tags and users.
Copper CRM, Inc. API docs- Source actions
- 34
- Destination actions
- 15
- Data types
- 24
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account1
- Get accountSource
The Copper account (organization) the key belongs to.
Activities4
- Log activityDestinationNot retried automaticallyApproval before production
Logs a user activity (for example a note, call or meeting type) on a record.
- Get activitySource
One activity.
- Search activitiesSource
Notes, calls, meetings and system activities, optionally for one parent record and date range.
- Update activityDestinationProvider duplicate protectionApproval before production
Updates the details or date of a user activity.
Activity types1
- List activity typesSource
User and system activity types.
Companies4
- Create companyDestinationNot retried automaticallyApproval before production
Creates a company.
- Get companySource
One company with custom fields.
- Search companiesSourceIncremental
Companies matching filters, optionally modified since a time.
- Update companyDestinationProvider duplicate protectionApproval before production
Updates mapped company fields; unmapped fields are left unchanged.
Contact types1
- List contact typesSource
Contact types for people and companies.
Custom activity types1
- List custom activity typesSource
Activity types (for example Phone Call, Meeting, To Do) used by activities and tasks.
Custom field definitions2
- Get custom field definitionSource
One custom field with data type, records it applies to and options.
- List custom field definitionsSource
Custom fields with data type, the records they apply to and dropdown options.
Customer sources1
- List customer sourcesSource
Customer sources for leads and opportunities.
Field layouts1
- List field layoutSource
Fields that apply to a record type, in display order, with required flags (opportunities need a pipeline).
Files2
- Get attached fileSource
Metadata of one attached file (file contents are not downloaded).
- List attached filesSource
Metadata of files attached to a lead, person, company, opportunity or project.
Lead statuses1
- List lead statusesSource
Lead statuses.
Leads5
- Create leadDestinationNot retried automaticallyApproval before production
Creates a lead.
- Get leadSource
One lead with custom fields.
- Search leadsSourceIncremental
Leads matching filters, optionally modified since a time.
- Update leadDestinationProvider duplicate protectionApproval before production
Updates mapped lead fields; unmapped fields are left unchanged.
- Upsert leadDestinationProvider duplicate protectionApproval before production
Updates the lead matching a name, email or custom field value, or creates one when none matches.
Loss reasons1
- List loss reasonsSource
Opportunity loss reasons.
Me1
- Get API userSource
The user who owns the API key.
Opportunities4
- Create opportunityDestinationNot retried automaticallyApproval before production
Creates a opportunity.
- Get opportunitySource
One opportunity with custom fields.
- Search opportunitiesSourceIncremental
Opportunities matching filters, optionally modified since a time.
- Update opportunityDestinationProvider duplicate protectionApproval before production
Updates mapped opportunity fields; unmapped fields are left unchanged.
People by email1
- Find person by emailSource
The person whose email matches exactly.
People4
- Create personDestinationNot retried automaticallyApproval before production
Creates a person.
- Get personSource
One person with custom fields.
- Search peopleSourceIncremental
People matching filters, optionally modified since a time.
- Update personDestinationProvider duplicate protectionApproval before production
Updates mapped person fields; unmapped fields are left unchanged.
Pipeline stages1
- List pipeline stagesSource
All pipeline stages with win probability, or only the stages of one pipeline.
Pipelines1
- List pipelinesSource
Opportunity pipelines with their stages.
Projects4
- Create projectDestinationNot retried automaticallyApproval before production
Creates a project.
- Get projectSource
One project with custom fields.
- Search projectsSourceIncremental
Projects matching filters, optionally modified since a time.
- Update projectDestinationProvider duplicate protectionApproval before production
Updates mapped project fields; unmapped fields are left unchanged.
Related records1
- List related recordsSource
IDs and types of records related to a lead, person, company, opportunity, project or task, optionally of one type.
Tags1
- List tagsSource
Tags with usage counts per record type.
Tasks4
- Create taskDestinationNot retried automaticallyApproval before production
Creates a task.
- Get taskSource
One task with custom fields.
- Search tasksSourceIncremental
Tasks matching filters, optionally modified since a time.
- Update taskDestinationProvider duplicate protectionApproval before production
Updates mapped task fields; unmapped fields are left unchanged.
Users2
- Get userSource
One user with the teams they belong to.
- List usersSource
Users in the Copper account.
Access and limits
- Authentication
- Copper API key with the token owner's email (X-PW-* headers)
- Plans and access
- API access on Copper Basic and above; the API key is generated by each user. The API key acts as the user whose email is sent with it and follows that user's permissions.
- Test environment
- Use a Copper trial account.
- Rate limits
- 180 requests per minute on a rolling window (bulk endpoints 3 per second); HTTP 429 when exceeded.
- Pagination
- Search endpoints take page_number and page_size (max 200); searches return at most 100,000 records.
- Provider events
- Webhook subscriptions for new, update and delete events on people, companies, leads, opportunities, tasks and projects. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Custom fields are written as definition ID/value pairs; fetch definitions with List custom field definitions.
- Timestamps are Unix seconds in Copper and are returned as ISO 8601 by Nexra; opportunity close_date stays in Copper's MM/DD/YYYY format.
- Copper has no idempotency key; uncertain creates are not repeated automatically. Lead upsert converges on the match field.
- Lead conversion, bulk endpoints, creating or removing related-record links, file uploads and downloads, custom field and activity type changes, webhook subscriptions and deletes are not automated.
- Related records, attached files and field layouts are read-only. File operations return metadata only.
- Person lookup by email (people_by_email.get) and people search by email send the address in the JSON body, never in the URL.
Developer reference
- Create the Copper CRM, Inc. credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Copper, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/copper and the Connections API.