> ## Documentation Index > Fetch the complete documentation index at: https://docs.withampersand.com/llms.txt > Use this file to discover all available pages before exploring further. # Copper ## What's Supported ### Supported Actions This connector supports: * [Write Actions](/write-actions). * [Read Actions](/read-actions), including full historic backfill and incremental read. * [Proxy Actions](/proxy-actions), using the base URL `https://api.copper.com/developer_api`. ### Supported Objects The Copper connector supports reading from and writing to the following objects: * [activities](https://developer.copper.com/activities/overview.html) * [companies](https://developer.copper.com/companies/overview.html) * [leads](https://developer.copper.com/leads/overview.html) * [opportunities](https://developer.copper.com/opportunities/overview.html) * [people](https://developer.copper.com/people/overview.html) * [projects](https://developer.copper.com/projects/overview.html) * [tasks](https://developer.copper.com/tasks/overview.html) The Copper connector supports reading from the following objects: * [activity\_types](https://developer.copper.com/activities/list-activity-types.html) * [contact\_types](https://developer.copper.com/people/list-contact-types.html) * [customer\_sources](https://developer.copper.com/leads/list-customer-sources.html#__tabbed_1_1) * [lead\_statuses](https://developer.copper.com/leads/list-lead-statuses.html) * [loss\_reasons](https://developer.copper.com/opportunities/list-loss-reasons.html) * [pipeline\_stages](https://developer.copper.com/opportunities/list-pipeline-stages.html) * [pipelines](https://developer.copper.com/opportunities/list-pipelines.html) * [tags](https://developer.copper.com/tags/overview.html) * [users](https://developer.copper.com/account-and-users/overview.html) #### Custom Fields In addition to standard fields, the connector supports any **custom fields** created through the Copper API. They behave the same way as built-in fields and can be queried alongside them. Copper does not provide a dedicated "field name" for custom fields. To represent them, the connector uses the **display name** rather than the numeric ID, and exposes it with the prefix `custom_field_`. * **Prefix**: Names always start with `custom_field_`. * **Display name**: Human-readable display names are used instead of IDs, with spaces replaced by underscores. > Example: A custom field with display name `Contract Start Date` in Copper is exposed as `custom_field_contract_start_date`. ## Before You Get Started To integrate Copper CRM with Ampersand, you must register *Copper CRM Oauth2* application. To register the application, you must contact `partners@copper.com` and provide the following details: * **Name** and **Purpose** of your application. * **URL** for an HTTPS endpoint that will handle the secure callback. If you want to connect via Ampersand, use the following callback URL: `https://api.withampersand.com/callbacks/v1/oauth`. After registering your application, you'll receive two credentials: **client\_id** and **client\_secret**. These are required to connect with Ampersand. ## Add Your Copper CRM App Info to Ampersand Once you have your Copper app set up and registered, you can proceed to connect it with Ampersand by following these steps: 1. Log in to your [Ampersand Dashboard](https://dashboard.withampersand.com). 2. Select the project where you want to create a Copper CRM integration. Ampersand Project Selection 3. Navigate to **Provider Apps**. 4. Select **Copper CRM** from the **Provider** list. 5. Enter the **Client ID** obtained from Copper in the **Client ID** field and the **Client Secret** in the **Client Secret** field. 6. Specify the scopes set for your application in Copper CRM. 7. Click **Save Changes** to complete the integration.