Reference · built on requestConnectorCRM & sales

Copper

Leads, people, companies, opportunities, and tasks from Copper through the Developer API and webhook subscriptions.

Request accessPricing ↗

About

Copper is a CRM built for teams that work in Google Workspace. Its Developer API at api.copper.com/developer_api returns leads, people, companies, opportunities, projects, tasks, and activities as JSON, with search, bulk create, and bulk update calls for the main record types. Webhook subscriptions post the ids of records that were created, updated, or deleted for seven entity types.

An operator on Fibric reads opportunities by pipeline and stage and proposes a task, a stage change, or a lead conversion. You approve each one; Copper is written once, and the receipt shows what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Copper and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Leads with their sources and statuses, through fetch, search, and convert calls
  • People fetched by id or by email, with contact types and activity history
  • Companies with contact types, related items, and activities
  • Opportunities with pipeline_id, pipeline_stage_id, status (Open, Won, Lost, Abandoned), monetary_value, close_date, and win_probability
  • Tasks and projects, with search and activity lists
  • Webhook notifications for new, update, and delete events on lead, person, company, opportunity, project, task, and activity_log

Proposed actions

  • Target capability: propose creating or updating a task tied to a lead, person, company, or opportunity
  • Target capability: propose moving an opportunity to another pipeline_stage_id or setting its status
  • Target capability: propose converting a lead into a person, company, and opportunity
  • Target capability: propose logging an activity on a record

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reach a new lead while it is still warm

    Subscribe to the lead new event, read the lead's source and status, and propose an owner, a first task, and a due time for approval.

    With Lead Response

  • Find the opportunities nobody has touched

    Search opportunities by pipeline and stage, compare date_modified against your threshold, and propose a follow-up task or a status change per deal.

    With Stale Pipeline

  • Catch a duplicate person at creation

    On a person new event, fetch by email and propose a merge task when a second record already carries that address.

    With Duplicate Lead

Requirements

  • A Copper account with a user who can generate an API key under System settings > API Keys
  • HTTPS with TLS 1.2 or higher on every request
  • An https:// endpoint to receive webhook notifications; Copper accepts no other scheme
  • A subscription plan within the cap of 100 active webhook subscriptions per account
Authentication
An API key generated under System settings > API Keys, sent as X-PW-AccessToken with X-PW-UserEmail and X-PW-Application: developer_api on every request; OAuth 2.0 is also available.

Limits

  • All API calls are capped at 180 requests per minute on a rolling window; bulk endpoints add a cap of 3 requests per second
  • Webhook notifications fire at most once per event and are never retried, whatever your endpoint returns
  • Update webhooks exclude relationship, activity, and metadata changes; notifications carry only record ids, 1 to 30 per message
  • Search returns at most the first 100,000 records regardless of page_number; page_size runs from 1 to 200

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Copper ↗

Questions and answers

Does Copper send webhooks for record changes?
Yes. You subscribe per entity type and event. Entity types are lead, person, company, opportunity, project, task, and activity_log; events are new, update, and delete. Each notification carries an array of 1 to 30 record ids, not the records, so a follow-up fetch is needed.
What headers does every Copper API request need?
Four: X-PW-AccessToken with the API key, X-PW-Application set to developer_api, X-PW-UserEmail with the address of the user who generated the key, and Content-Type: application/json. Requests must use HTTPS with TLS 1.2 or higher.
How is Copper's rate limit enforced?
Copper limits all API calls to 180 requests per minute on a rolling window and bulk calls to 3 per second; beyond either cap it returns 429. Webhooks are limited separately, to 600 notifications per minute and 1,800 per 10 minutes per account.
Ask about Copper

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Copper through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy